CVE-2026-29181

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — Patch released this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 7, 2026

Last Modified

September 17, 2026

Advisory Details (5)

Auto-updated Jul 6, 2026
Patch available. Sources: github, redhat.
Red Hat

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
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-29181
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:25271
GitHub advisoryMentions a patch (unverified)

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

Patch Availability(12)

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 rangeFix by version rangeDependents
go.opentelemetry.io/otel—
  • 1.36.0 up to 1.41.0: fixed in 1.41.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 297 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 202 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-29181?
CVE-2026-29181 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-29181 published?
The CVE record for CVE-2026-29181 was published on April 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-29181 actively exploited?
CVE-2026-29181 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-29181?
CVE-2026-29181 has a CVSS base score of 7.5 (the CNA's own assessment, by github_m; NVD's own analysis pending).
How do I remediate CVE-2026-29181?
A fix for CVE-2026-29181 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-29181 are linked in the Vendor Advisories panel on this page.

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.