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.
CVE-2026-39882
MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 8.8%
- KEV
- Not listed
Published
April 8, 2026
Last Modified
April 9, 2026
References (2)
- security-advisories@githubhttps://github.com/open-telemetry/opentelemetry-go/pull/8108
- security-advisories@githubhttps://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58
Vendor Advisories for CVE-2026-39882(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 1 ecosystem)
Go(3)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp | — | 0.19.0 | — |
| go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp | — | 1.43.0 | — |
| go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp | — | 1.43.0 | — |
Frequently asked(5)
What is CVE-2026-39882?
CVE-2026-39882 is a medium vulnerability published on April 8, 2026. 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…
When was CVE-2026-39882 disclosed?
CVE-2026-39882 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on April 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39882 actively exploited?
CVE-2026-39882 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-39882?
CVE-2026-39882 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-39882?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39882, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39882
Is Your Infrastructure Affected by CVE-2026-39882?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.