CVE-2026-39882 | OpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies

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.

Published: 2026-04-08 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-39882 is rated Low Risk (24.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.19%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-39882

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.19% +0.17%
2 2026-04-09 0.02%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-39882

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.6 3.6 [email protected]

Weakness enumeration for CVE-2026-39882

GitHub Security Advisory for CVE-2026-39882

GHSA-w8rr-5gcm-pp58 · Severity: medium · Ecosystem: go — opentelemetry-go: OTLP HTTP exporters read unbounded HTTP response bodies

OS Trackers for CVE-2026-39882

vendor priority summary link
debian not yet assigned CVE-2026-39882 not yet assigned priority: Debian including 1 source packages (golang-opentelemetry-otel), 4 status rows across 4 suites (bookworm, forky, sid, trixie): open 2, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-39882
ubuntu medium CVE-2026-39882 medium priority: Ubuntu including 1 source packages (golang-opentelemetry-otel), 4 status rows across 4 suites (jammy, noble, questing, upstream): needs-triage 4. https://ubuntu.com/security/CVE-2026-39882

Affected software / configurations for CVE-2026-39882

Vendor Product Version Raw CPE
opentelemetry opentelemetry < 1.43.0 cpe:2.3:a:opentelemetry:opentelemetry:*:*:*:*:*:go:*:*

References for CVE-2026-39882

cvelogic Threat Intelligence