Lucene search
+L

5 matches found

SUSE CVE
SUSE CVE
•added 2026/07/30 4:47 p.m.•14 views

SUSE CVE-2026-45287

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.0.17, go.opentelemetry.io/otel/schema/v1.0 and go.opentelemetry.io/otel/schema/v1.1 leaks one file descriptor on each successful ParseFile call. ParseFile opens the schema file and passes it to Parse without closing it...

5.5CVSS7.8AI score0.00175EPSS
SaveExploits1References2
Debian CVE
Debian CVE
•added 2026/06/29 7:38 p.m.•33 views

CVE-2026-56018

JavaScript::Minifier::XS versions before 0.16 for Perl leak memory on every call to minify, allowing unbounded memory growth. In JsMinify XS.xs the cleanup frees only the NodeSet structures and never the per-token contents buffers allocated in JsSetNodeContents; JsDiscardNode unlinks nodes withou...

7.5CVSS5.8AI score0.00609EPSS
SaveExploits0
CVE
CVE
•added 2026/06/04 2:45 p.m.•110 views

CVE-2026-45287

OpenTelemetry-Go (Go implementation) prior to version 0.0.17 leaks one file descriptor per successful ParseFile call when parsing go.opentelemetry.io/otel/schema/v1.0 and v1.1. In long-running processes, repeated schema parsing without proper file closure can exhaust the process file descriptor l...

5.5CVSS7.8AI score0.00175EPSS
SaveExploits1References3Affected Software1
RedHat Linux
RedHat Linux
•added 2026/06/04 12:41 p.m.•22 views

go.opentelemetry.io/otel: go.opentelemetry.io/otel/schema/v1.0: go.opentelemetry.io/otel/schema/v1.1: OpenTelemetry-Go: Denial of Service due to file descriptor leak

A flaw was found in OpenTelemetry-Go before schema package version 0.0.17. ParseFile in go.opentelemetry.io/otel/schema/v1.0 and v1.1 opens a schema file and passes it to Parse without closing it, leaking one file descriptor per successful call. Repeated parsing in a long-running process can...

5.5CVSS7.8AI score0.00175EPSS
SaveExploits1References7
OSV
OSV
•added 2020/01/21 6:15 p.m.•8 views

DEBIAN-CVE-2019-14907

All samba versions 4.9.x before 4.9.18, 4.10.x before 4.10.12 and 4.11.x before 4.11.5 have an issue where if it is set with "log level = 3" or above then the string obtained from the client, after a failed character conversion, is printed. Such strings can be provided during the NTLMSSP...

6.5CVSS6.6AI score0.03151EPSS
SaveExploits0References1
Rows per page
Query Builder