Uncontrolled Memory Allocation Affecting prometheus-3.10 package, versions <3.10.0-r3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-PROMETHEUS310-16009841
- published13 Apr 2026
- disclosed8 Apr 2026
Introduced: 8 Apr 2026
NewCVE-2026-39882 (opens in a new tab)How to fix?
Upgrade Minimos:latest prometheus-3.10 to version 3.10.0-r3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream prometheus-3.10 package and not the prometheus-3.10 package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.
References
- https://www.cve.org/CVERecord?id=CVE-2026-39882
- https://github.com/advisories/GHSA-w8rr-5gcm-pp58
- https://osv.dev/vulnerability/MINI-8hpq-prhh-qp9f
- https://osv.dev/vulnerability/CVE-2026-39882
- https://github.com/open-telemetry/opentelemetry-go/pull/8108
- https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58