CVE-2026-29181: open-telemetry opentelemetry-go · Unthrottled Resource Allocation
Affects open-telemetry opentelemetry-goSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.41.0 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.41.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade opentelemetry-go and github.com/open-telemetry/opentelemetry-go to 1.41.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| open-telemetryopentelemetry-go | Affected
| Fixed in
|
Gogithub.com/open-telemetry/opentelemetry-gopkg:golang/github.com/open-telemetry/opentelemetry-goOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in OpenTelemetry-Go version 1.41.0. Users should upgrade to this version or later to remediate the vulnerability. Red Hat customers should follow the vendor advisories and upgrade affected products accordingly. No alternative mitigations or temporary fixes are documented in the advisory.
Description
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.
References
- github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-29181 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2456252 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-29181.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:25271 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:47735 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:61314 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:63140 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:66521 (opens in a new tab)