CVE-2026-29181

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% 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, secondary
Trending — Patch released this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

April 7, 2026

Last Modified

September 4, 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(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcluster-observability-operator/cluster-observability-rhel9-operator:17875936372026-08-31redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17847387582026-07-29redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17809178812026-06-11redhat

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

(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 15× in last 7d / 92× 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 245 total refreshes for this CVE.

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

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 September 4, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 50.4% of all scored CVEs.
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