CVE-2026-128086
OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.0.0-RC1 until version 1.47.0, baggage.Parse and propagation.Baggage.Extract eagerly materialize every W3C baggage property through parseMember, grow property slices, serialize members, and copy properties into internal/baggage.Item. A valid densely populated baggage header can therefore cause allocation traffic and retained memory disproportionate to its bounded input size. Remote impact requires baggage extraction to be enabled, attacker-controlled input to reach it, and extraction to run before authentication or on a public route; the evidence establishes increased allocation and garbage-collection pressure but not reliable process termination. This issue is fixed in version 1.47.0.
Fixes and workarounds
Fix
go.opentelemetry.io/otel/baggage (Go): OSV reports a fixed version 1.47.0. Check the advisory for supported release branches.
Source: OSV GHSA-rrfc-gjm9-cgrjFix
go.opentelemetry.io/otel/propagation (Go): OSV reports a fixed version 1.47.0. Check the advisory for supported release branches.
Source: OSV GHSA-rrfc-gjm9-cgrjAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| opentelemetry-go open-telemetry |
>= 1.0.0-RC1, < 1.47.0 (affected) | CNA: GitHub_M |
go.opentelemetry.io/otel/baggagego.opentelemetry.io/otel/baggage
Go |
≥ 1.0.0-RC1; < 1.47.0 (affected, semver); OSV events: introduced 1.0.0-RC1; fixed 1.47.0Source events (semver)Other versions: unaffected |
OSV GHSA-rrfc-gjm9-cgrj |
go.opentelemetry.io/otel/propagationgo.opentelemetry.io/otel/propagation
Go |
≥ 1.0.0-RC1; < 1.47.0 (affected, semver); OSV events: introduced 1.0.0-RC1; fixed 1.47.0Source events (semver)Other versions: unaffected |
OSV GHSA-rrfc-gjm9-cgrj |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 5.3 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA: GitHub_M |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-rrfc-gjm9-cgrjCNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/open-telemetry/opentelemetry-go/pull/9024CNA: GitHub_M · x_refsource_MISC
- https://github.com/open-telemetry/opentelemetry-go/commit/f09d1de32f4ac7e5ef16394533721106b1a57b89CNA: GitHub_M · x_refsource_MISC
- https://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.47.0CNA: GitHub_M · x_refsource_MISC
- https://github.com/advisories/GHSA-rrfc-gjm9-cgrjOSV / GitHub Security Advisories · advisory
- https://osv.dev/vulnerability/GHSA-rrfc-gjm9-cgrjOSV / GitHub Security Advisories · osv
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.