CVE-2026-29181

opentelemetry-go · Vulnerability

CVSS 3.1 7.5 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.5 HIGHCVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by go.opentelemetry.io/otel 1.41.0osv · severity unknownFixed by go.opentelemetry.io/otel 1.41.0KEV status unknown

Original advisory

cve-program · CVE-2026-29181

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-19938

Published

Read the publisher's advisory

nvd · CVE-2026-29181

Published

Read the publisher's advisory

osv · GHSA-mh2q-q3fh-2475

Published

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. ## severity HIGH (availability / remote request amplification) ## relevant links - repository: https://github.com/open-telemetry/opentelemetry-go - pinned callsite: https://github.com/open-telemetry/opentelemetry-go/blob/1ee4a4126dbdd1bc79e9fae072fa488beffac52a/propagation/baggage.go#L58 ## vulnerability details **pins:** open-telemetry/opentelemetry-go@1ee4a4126dbdd1bc79e9fae072fa488beffac52a **as-of:** 2026-02-04 **policy:** direct (no program scope provided) **callsite:** propagation/baggage.go:58 (`extractMultiBaggage`) **attacker control:** inbound HTTP request headers (many `baggage` field-values) → `propagation.HeaderCarrier.Values("baggage")` → repeated `baggage.Parse` + member aggregation ### root cause `extractMultiBaggage` iterates over all `baggage` header field-values and parses each one independently, then appends members into a shared slice. the 8192-byte parsing cap applies per header value, but the multi-value path repeats that work once per header line (bounded only by the server/proxy header byte limit). ### impact in a default `net/http` configuration (max header bytes 1mb), a single request with many `baggage:` header field-values can cause large per-request allocations and increased latency. example from the attached PoC harness (darwin/arm64; 80 values; 40 requests): - canonical: `per_req_alloc_bytes=10315458` and `p95_ms=7` - control: `per_req_alloc_bytes=133429` and `p95_ms=0` ## proof of concept canonical: ```bash mkdir -p poc unzip poc.zip -d poc cd poc make test ``` output (excerpt): ``` [CALLSITE_HIT]: propagation/baggage.go:58 extractMultiBaggage [PROOF_MARKER]: baggage_multi_value_amplification p95_ms=7 per_req_alloc_bytes=10315458 per_req_allocs=16165 ``` control: ```bash cd poc make control ``` control output (excerpt): ``` [NC_MARKER]: baggage_single_value_baseline p95_ms=0 per_req_alloc_bytes=133429 per_req_allocs=480 ``` **expected:** multiple `baggage` header field-values should be semantically equivalent to a single comma-joined `baggage` value and should not multiply parsing/alloc work within the effective header byte budget. **actual:** multiple `baggage` header field-values trigger repeated parsing and member aggregation, causing high per-request allocations and increased latency even when each individual value is within 8192 bytes. ## fix recommendation avoid repeated parsing across multi-values by enforcing a global budget and/or normalizing multi-values into a single value before parsing. one mitigation approach is to treat multi-values as a single comma-joined string and cap total parsed bytes (for example 8192 bytes total). **fix accepted when:** under the default PoC harness settings, canonical stays within 2x of control for `per_req_alloc_bytes` and `per_req_allocs`, and `p95_ms` stays below 2ms. [poc.zip](https://github.com/user-attachments/files/25079945/poc.zip) [PR_DESCRIPTION.md](https://github.com/user-attachments/files/25079946/PR_DESCRIPTION.md)

Read the publisher's advisory

osv · GO-2026-5506

Published

OpenTelemetry-Go: Multi-value baggage header extraction causes excessive allocations in go.opentelemetry.io/otel

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-29181

Published

OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)

Source published: 7 Apr 2026 20:29:13 UTC
Source modified: 17 Sep 2026 12:04:31 UTC
Saved here: 23 Oct 2026 15:48:27 UTC
Source terms: CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

euvd · EUVD-2026-19938

Published

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 …

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Apr 7, 2026, 8:29:13 PM

dateUpdated: Sep 17, 2026, 12:04:31 PM

15 related source bulletins · separate from aliases

msrc_CVE-2026-29181: OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)

CVE-2026-29181

openSUSE-SU-2026:11173-1: etcd-3.6.13-1.1 on GA media

CVE-2026-29181 · CVE-2026-39883

RHSA-2026:63140: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.19.2

CVE-2026-1965 · CVE-2026-3783 · CVE-2026-8286 · CVE-2026-9547 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-15588 · CVE-2026-29181 · CVE-2026-39883 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58055

RHSA-2026:70870: Red Hat Security Advisory: Logging for Red Hat OpenShift - 6.5.3

CVE-2026-18140 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-29181 · CVE-2026-33818 · CVE-2026-35469 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-41178 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42502 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46600 · CVE-2026-46604 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862

RHSA-2026:66521: Red Hat Security Advisory: Logging for Red Hat OpenShift - 6.6.1

CVE-2026-15792 · CVE-2026-17106 · CVE-2026-18140 · CVE-2026-29181 · CVE-2026-33818 · CVE-2026-35469 · CVE-2026-39828 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39835 · CVE-2026-41178 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46604 · CVE-2026-56852 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-75593

RHSA-2026:47735: Red Hat Security Advisory: multicluster engine for Kubernetes v2.8.9 security update

CVE-2026-16242 · CVE-2026-17107 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-29181 · CVE-2026-33811 · CVE-2026-39821 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-44990 · CVE-2026-45447 · CVE-2026-59869

RHSA-2026:83013: Red Hat Security Advisory: Logging for Red Hat OpenShift - 6.0.17

CVE-2026-18140 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-29181 · CVE-2026-32283 · CVE-2026-32285 · CVE-2026-33186 · CVE-2026-33818 · CVE-2026-35469 · CVE-2026-41178 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42499 · CVE-2026-42502 · CVE-2026-46600 · CVE-2026-56852 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-63209 · CVE-2026-84445

RHSA-2026:72395: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.20.1

CVE-2025-6170 · CVE-2026-1965 · CVE-2026-3783 · CVE-2026-5435 · CVE-2026-5928 · CVE-2026-6238 · CVE-2026-6653 · CVE-2026-8286 · CVE-2026-8458 · CVE-2026-8927 · CVE-2026-9547 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-11979 · CVE-2026-13757 · CVE-2026-14164 · CVE-2026-14456 · CVE-2026-14457 · CVE-2026-15588 · CVE-2026-16118 · CVE-2026-18798 · CVE-2026-29181 · CVE-2026-33186 · CVE-2026-39883 · CVE-2026-41989 · CVE-2026-46600 · CVE-2026-48864 · CVE-2026-54369 · CVE-2026-54370 · CVE-2026-54371 · CVE-2026-54874 · CVE-2026-56392 · CVE-2026-56852 · CVE-2026-56854 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58016 · CVE-2026-58055 · CVE-2026-63072 · CVE-2026-63073 · CVE-2026-63074 · CVE-2026-63075 · CVE-2026-63076 · CVE-2026-63379 · CVE-2026-63381 · CVE-2026-63382 · CVE-2026-63383 · CVE-2026-63384 · CVE-2026-63385 · CVE-2026-63387 · CVE-2026-63388 · CVE-2026-81870 · CVE-2026-84445

WID-SEC-W-2026-3046: IBM Concert: Mehrere Schwachstellen

CVE-2019-19921 · CVE-2021-23337 · CVE-2024-3651 · CVE-2024-39338 · CVE-2024-45590 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-15599 · CVE-2025-22874 · CVE-2025-47273 · CVE-2025-47907 · CVE-2025-52881 · CVE-2025-53643 · CVE-2025-55184 · CVE-2025-58056 · CVE-2025-58188 · CVE-2025-58189 · CVE-2025-61723 · CVE-2025-61730 · CVE-2025-64649 · CVE-2025-64756 · CVE-2025-67221 · CVE-2025-68121 · CVE-2025-68146 · CVE-2026-0540 · CVE-2026-2327 · CVE-2026-23490 · CVE-2026-23897 · CVE-2026-2391 · CVE-2026-23949 · CVE-2026-24486 · CVE-2026-25528 · CVE-2026-25547 · CVE-2026-25639 · CVE-2026-25990 · CVE-2026-26007 · CVE-2026-26019 · CVE-2026-26996 · CVE-2026-27142 · CVE-2026-27212 · CVE-2026-27699 · CVE-2026-27903 · CVE-2026-27904 · CVE-2026-28684 · CVE-2026-29063 · CVE-2026-29181 · CVE-2026-2950 · CVE-2026-31808 · CVE-2026-31900 · CVE-2026-32274 · CVE-2026-32288 · CVE-2026-32597 · CVE-2026-32630 · CVE-2026-32887 · CVE-2026-32952 · CVE-2026-33186 · CVE-2026-33532 · CVE-2026-33750 · CVE-2026-33814 · CVE-2026-33816 · CVE-2026-33916 · CVE-2026-34043 · CVE-2026-34073 · CVE-2026-34077 · CVE-2026-3520 · CVE-2026-35469 · CVE-2026-35515 · CVE-2026-3627 · CVE-2026-39823 · CVE-2026-39825 · CVE-2026-39826 · CVE-2026-39892 · CVE-2026-39984 · CVE-2026-40175 · CVE-2026-40179 · CVE-2026-40181 · CVE-2026-40190 · CVE-2026-40347 · CVE-2026-41066 · CVE-2026-41182 · CVE-2026-41238 · CVE-2026-41239 · CVE-2026-41240 · CVE-2026-41305 · CVE-2026-41324 · CVE-2026-41425 · CVE-2026-41481 · CVE-2026-41488 · CVE-2026-41602 · CVE-2026-41636 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42198 · CVE-2026-42211 · CVE-2026-42338 · CVE-2026-42342 · CVE-2026-42561 · CVE-2026-42577 · CVE-2026-43870 · CVE-2026-44405 · CVE-2026-44431 · CVE-2026-44432 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44496 · CVE-2026-44728 · CVE-2026-4539 · CVE-2026-45409 · CVE-2026-45736 · CVE-2026-46625 · CVE-2026-4800 · CVE-2026-4923 · CVE-2026-4926 · CVE-2026-7246 · CVE-2026-8723

RHSA-2026:25271: Red Hat Security Advisory: multicluster engine for Kubernetes v2.11.0 General Availability

CVE-2026-6322 · CVE-2026-29181 · CVE-2026-40895 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42039 · CVE-2026-42041 · CVE-2026-42043 · CVE-2026-42044

RHSA-2026:72475: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.20.1

RHSA-2026:61314: Red Hat Security Advisory: Cluster Observability Operator 1.5.2

CVE-2026-13676 · CVE-2026-27145 · CVE-2026-29181 · CVE-2026-32281 · CVE-2026-32285 · CVE-2026-35469 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-41178 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46600 · CVE-2026-55677 · CVE-2026-56852 · CVE-2026-73643

RHSA-2026:68349: Red Hat Security Advisory: Logging for Red Hat OpenShift - 6.2.13

CVE-2026-15792 · CVE-2026-18140 · CVE-2026-29181 · CVE-2026-32283 · CVE-2026-33818 · CVE-2026-35469 · CVE-2026-41178 · CVE-2026-42502 · CVE-2026-56852 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862

RHSA-2026:82322: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.17.2

CVE-2024-34459 · CVE-2025-5278 · CVE-2025-6170 · CVE-2025-13151 · CVE-2025-14087 · CVE-2025-14512 · CVE-2025-47911 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-58181 · CVE-2025-58190 · CVE-2026-1965 · CVE-2026-2100 · CVE-2026-2673 · CVE-2026-3783 · CVE-2026-3832 · CVE-2026-3833 · CVE-2026-4046 · CVE-2026-4424 · CVE-2026-4437 · CVE-2026-4438 · CVE-2026-4878 · CVE-2026-5121 · CVE-2026-5260 · CVE-2026-5419 · CVE-2026-5435 · CVE-2026-5450 · CVE-2026-5928 · CVE-2026-6238 · CVE-2026-6653 · CVE-2026-7383 · CVE-2026-8286 · CVE-2026-9076 · CVE-2026-9547 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-11979 · CVE-2026-13757 · CVE-2026-14164 · CVE-2026-15588 · CVE-2026-16118 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-27135 · CVE-2026-27136 · CVE-2026-28390 · CVE-2026-29111 · CVE-2026-29181 · CVE-2026-31790 · CVE-2026-33186 · CVE-2026-33845 · CVE-2026-33846 · CVE-2026-34180 · CVE-2026-34181 · CVE-2026-34182 · CVE-2026-34183 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-40355 · CVE-2026-40356 · CVE-2026-41989 · CVE-2026-42009 · CVE-2026-42010 · CVE-2026-42011 · CVE-2026-42012 · CVE-2026-42013 · CVE-2026-42014 · CVE-2026-42015 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-42764 · CVE-2026-42766 · CVE-2026-42767 · CVE-2026-42768 · CVE-2026-42769 · CVE-2026-42770 · CVE-2026-45445 · CVE-2026-45446 · CVE-2026-45447 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598 · CVE-2026-46600 · CVE-2026-48864 · CVE-2026-54369 · CVE-2026-54370 · CVE-2026-54371 · CVE-2026-56854 · CVE-2026-56855 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58016 · CVE-2026-58055 · CVE-2026-78662 · CVE-2026-84304 · CVE-2026-84445

RHSA-2026:82336: Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.17.1

CVE-2025-6170 · CVE-2026-1965 · CVE-2026-3783 · CVE-2026-5435 · CVE-2026-5928 · CVE-2026-6238 · CVE-2026-6653 · CVE-2026-8286 · CVE-2026-9547 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-11979 · CVE-2026-13757 · CVE-2026-14164 · CVE-2026-15588 · CVE-2026-16118 · CVE-2026-29181 · CVE-2026-41989 · CVE-2026-48864 · CVE-2026-54369 · CVE-2026-54370 · CVE-2026-54371 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58016 · CVE-2026-58055

Source published: Apr 7, 2026, 8:29:13 PM (timezone not stated)
Source modified: Sep 17, 2026, 12:04:31 PM (timezone not stated)
Saved here: 11 Nov 2026 07:35:30 UTC
Source terms: ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd · CVE-2026-29181

Published

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 …

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-770

Original publisher date fields

published: 2026-04-07T21:17:16.003

lastModified: 2026-09-11T13:17:25.487

1 source CPE criteria · context only

cpe:2.3:a:opentelemetry:opentelemetry:*:*:*:*:*:go:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published: 7 Apr 2026 21:17:16 UTC
Source modified: 11 Sep 2026 13:17:25 UTC
Saved here: 25 Oct 2026 07:19:08 UTC
Source terms: NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

osv · GHSA-mh2q-q3fh-2475

Published

OpenTelemetry-Go: multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)

Source published: 7 Apr 2026 20:12:57 UTC
Source modified: 10 Sep 2026 03:51:02 UTC
Saved here: 24 Oct 2026 13:19:41 UTC
Source terms: GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Publisher rating · HIGH

osv · GO-2026-5506

Published

OpenTelemetry-Go: Multi-value baggage header extraction causes excessive allocations in go.opentelemetry.io/otel

Source published: 24 Jul 2026 18:35:55 UTC
Source modified: 6 Aug 2026 15:11:52 UTC
Saved here: 24 Oct 2026 13:19:41 UTC
Source terms: OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.