CVE-2026-29181

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 77% 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
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.36.0 to 1.40.0, multi-value baggage: header extraction parses each header field-value independently and aggregates members across values. This allows an attacker to amplify cpu and allocations by sending many baggage: header lines, even when each individual value is within the 8192-byte per-value parse limit. This vulnerability is fixed in 1.41.0.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
35.1%
KEV
Not listed

Published

April 7, 2026

Last Modified

June 30, 2026

Advisory Details (5)

Auto-updated Jul 6, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-29181.json
redhat

2456252 – (CVE-2026-29181) CVE-2026-29181 github.com/open-telemetry/opentelemetry-go: OpenTelemetry-Go: Denial of Service via crafted multi-value baggage headers

https://bugzilla.redhat.com/show_bug.cgi?id=2456252
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-29181
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:25271
github Patch Available🟡 PoC Available

multi-value `baggage` header extraction causes excessive allocations (remote dos amplification) · Advisory · open-telemetry/opentelemetry-go · GitHub

https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475

Vendor Advisories for CVE-2026-29181(2)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
go.opentelemetry.io/otel—1.41.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 43× 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 106 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-29181?
CVE-2026-29181 is a high vulnerability published on April 7, 2026. OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.36.0 to 1.40.0, multi-value baggage: header extraction parses each header field-value independently and aggregates members across values. This allows an attacker to amplify cpu and allocations by sending many baggage: header lines,…
When was CVE-2026-29181 disclosed?
CVE-2026-29181 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-29181 actively exploited?
CVE-2026-29181 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-29181?
CVE-2026-29181 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-29181?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-29181, 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-29181

Explore →

Is Your Infrastructure Affected by CVE-2026-29181?

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

Start Free Scan →Browse All CVEs