CVE-2026-39882: medium-severity vulnerability in open-telemetry opentelemetry-go
OpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.2%
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.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
open-telemetry · opentelemetry-goRelated CVEs — open-telemetry opentelemetry-go
In the same product, most dangerous first.
CVE-2026-29181HIGHOpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)EPSS 0.8%CVE-2026-128085MEDIUMopentelemetry-go: AttributeValueLengthLimit is fully bypassed by attribute values composed of valid U+FFFD runesEPSS 0.5%CVE-2026-128086MEDIUMOpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplificationEPSS 0.4%CVE-2026-81872MEDIUMOpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is fullEPSS 0.4%CVE-2026-81870LOWOpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logsEPSS 0.3%CVE-2026-39883HIGHOpenTelemetry-Go has an incomplete fix for CVE-2026-24051: BSD kenv command not using absolute path enables PATH hijackingEPSS 0.3%