CVE-2026-29181
Opentelemetry denial of service
- Published7 Apr 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:25271
- https://access.redhat.com/errata/RHSA-2026:47735
- https://access.redhat.com/errata/RHSA-2026:61314
- https://access.redhat.com/errata/RHSA-2026:63140
- https://access.redhat.com/errata/RHSA-2026:66521
- https://access.redhat.com/security/cve/CVE-2026-29181
- https://bugzilla.redhat.com/show_bug.cgi?id=2456252
- https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-29181.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-29181 being actively exploited?
CVE-2026-29181 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.87%.
How severe is CVE-2026-29181?
CVE-2026-29181 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.87% probability of exploitation.
Which products are affected by CVE-2026-29181?
Affected products include Opentelemetry.
How do I fix CVE-2026-29181?
Upgrade affected software to a fixed version, for example Opentelemetry 1.41.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-29181 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.