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.2%, top 91% 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.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

April 8, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jul 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github.
github Patch Available🟡 PoC Available

OTLP HTTP exporters read unbounded HTTP response bodies · Advisory · open-telemetry/opentelemetry-go · GitHub

https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58
github_pr

limit response body size for OTLP HTTP exporters

Fix merged in open-telemetry/opentelemetry-go PR #8108 on 2026-04-01 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-go/pull/8108

Vendor Advisories for CVE-2026-39882(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-thanos-rhel9:17829775132026-07-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 4 ecosystems)
Go(3)
PackageVulnerable rangeFixed inDependents
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—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-opentelemetry-otel1.1.0-2 ... 1.43.0-4 (19 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-opentelemetry-otel1.31.0-4 ... 1.43.0-4 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-opentelemetry-otel1.31.0-4, 1.31.0-5, 1.31.0-61.43.0-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 143 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 07:17 UTCEG score recompute
  9. 2026-08-16 07:17 UTCVendor advisory
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 05:13 UTCEG score recompute
  13. 2026-08-14 05:13 UTCVendor advisory
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 19:28 UTCEG score recompute
  16. 2026-08-12 19:28 UTCVendor advisory
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-11 13:43 UTCEPSS rescore
  19. 2026-08-11 08:24 UTCEG score recompute
  20. 2026-08-11 08:24 UTCVendor advisory
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-10 06:31 UTCEG score recompute
  23. 2026-08-10 06:31 UTCVendor advisory
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 04:42 UTCEG score recompute
Show 75 more
  1. 2026-08-09 04:42 UTCVendor advisory
  2. 2026-08-07 14:36 UTCEG score recompute
  3. 2026-08-07 14:36 UTCVendor advisory
  4. 2026-08-06 13:46 UTCEPSS rescore
  5. 2026-08-05 23:50 UTCEG score recompute
  6. 2026-08-05 23:50 UTCVendor advisory
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 15:10 UTCEPSS rescore
  9. 2026-08-04 10:38 UTCEPSS rescore
  10. 2026-08-03 22:06 UTCEG score recompute
  11. 2026-08-03 22:06 UTCVendor advisory
  12. 2026-08-03 10:36 UTCEPSS rescore
  13. 2026-08-02 14:02 UTCEG score recompute
  14. 2026-08-02 14:02 UTCVendor advisory
  15. 2026-08-02 02:27 UTCEPSS rescore
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 01:30 UTCEPSS rescore
  19. 2026-07-27 14:13 UTCEPSS rescore
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 08:42 UTCEG score recompute
  23. 2026-07-26 08:42 UTCVendor advisory
  24. 2026-07-25 14:18 UTCEPSS rescore
  25. 2026-07-25 14:18 UTCEPSS rescore
  26. 2026-07-24 14:17 UTCEPSS rescore
  27. 2026-07-24 14:17 UTCEPSS rescore
  28. 2026-07-23 14:18 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 03:10 UTCEG score recompute
  31. 2026-07-22 14:08 UTCEPSS rescore
  32. 2026-07-21 15:24 UTCEPSS rescore
  33. 2026-07-20 21:02 UTCOSV refresh
  34. 2026-07-20 17:08 UTCEPSS rescore
  35. 2026-07-19 14:31 UTCEPSS rescore
  36. 2026-07-19 02:29 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-16 17:03 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 02:00 UTCEPSS rescore
  42. 2026-07-13 22:30 UTCEPSS rescore
  43. 2026-07-13 06:13 UTCEPSS rescore
  44. 2026-07-13 06:13 UTCEPSS rescore
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-11 08:27 UTCEPSS rescore
  47. 2026-07-09 19:10 UTCEPSS rescore
  48. 2026-07-08 15:15 UTCEPSS rescore
  49. 2026-07-07 13:46 UTCEPSS rescore
  50. 2026-07-06 16:27 UTCEPSS rescore
  51. 2026-07-06 16:27 UTCEPSS rescore
  52. 2026-07-06 02:23 UTCEPSS rescore
  53. 2026-07-06 02:23 UTCEPSS rescore
  54. 2026-07-05 02:30 UTCEPSS rescore
  55. 2026-07-04 06:31 UTCEPSS rescore
  56. 2026-07-01 15:06 UTCEPSS rescore
  57. 2026-06-30 23:22 UTCEPSS rescore
  58. 2026-06-29 14:06 UTCEPSS rescore
  59. 2026-06-28 14:07 UTCEPSS rescore
  60. 2026-06-28 04:56 UTCEPSS rescore
  61. 2026-06-27 03:08 UTCEPSS rescore
  62. 2026-06-25 13:49 UTCEPSS rescore
  63. 2026-06-25 13:49 UTCEPSS rescore
  64. 2026-06-24 14:05 UTCEPSS rescore
  65. 2026-06-23 21:33 UTCEPSS rescore
  66. 2026-06-22 14:25 UTCEPSS rescore
  67. 2026-06-22 14:25 UTCEPSS rescore
  68. 2026-06-21 14:56 UTCEPSS rescore
  69. 2026-06-21 14:56 UTCEPSS rescore
  70. 2026-06-21 01:59 UTCEPSS rescore
  71. 2026-06-19 19:25 UTCEPSS rescore
  72. 2026-06-18 17:52 UTCEPSS rescore
  73. 2026-06-18 17:52 UTCEPSS rescore
  74. 2026-06-17 17:53 UTCEPSS rescore
  75. 2026-06-16 17:52 UTCEPSS rescore

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 July 24, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 91.3% of all scored CVEs.
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

Explore →

Is Your Infrastructure Affected by CVE-2026-39882?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs