CVE-2026-39882

unknown

Published 2026-04-08 · Modified 2026-05-27

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS v4 NEW

—

not yet in upstream

VIR risk

—

Description

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.

Predictions

Exploit likelihood

20%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OS	Version	Status	Fixed in
debian	bookworm	affected
debian	forky	affected
debian	sid	fixed	`1.43.0-1`
debian	trixie	affected

Package impact

Ecosystem	Package	Vulnerable	Fixed
Go	go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp	`<1.43.0`	`1.43.0`
Go	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp	`<1.43.0`	`1.43.0`
Go	go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp	`<0.19.0`	`0.19.0`

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.