Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-128086

OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification

No exploitation reported by the sources we read.

  • Published2026-11-13
  • Fixed in1.47.0
  • WeaknessCWE-400 · CWE-405

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-11-1318:54CVE publishedCNA

Versions per branch

OSV
go.opentelemetry.io/otel/baggage
BranchAffectedFixed in
1.x≥ 1.0.0-RC1, < 1.47.01.47.0
go.opentelemetry.io/otel/propagation
BranchAffectedFixed in
1.x≥ 1.0.0-RC1, < 1.47.01.47.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • open-telemetry opentelemetry-go
    Affected
    • = >= 1.0.0-RC1, < 1.47.0no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-13

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • aws-ebs-csi-driverMinimOSall versions · fixed in 1.66.1-r0and 1 other package
  • aws-iam-authenticator-fipsMinimOSall versions · fixed in 0.7.21-r0
  • azure-service-operatorMinimOSall versions · fixed in 2.22.0-r0
  • bufMinimOSall versions · fixed in 1.74.0-r0and 1 other package
  • buildkite-mcpMinimOSall versions · fixed in 1.26.1-r0and 1 other package
  • buildpacks-lifecycle-0.21MinimOSall versions · fixed in 0.21.26-r0and 1 other package
  • cerbosMinimOSall versions · fixed in 0.57.0-r0and 1 other package
  • cert-manager-google-cas-issuerMinimOSall versions · fixed in 0.14.0-r0and 1 other package

24 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update go.opentelemetry.io/otel/baggage to 1.47.0

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Published
2026-11-13
Last Modified
2026-11-16
NVD status
Received
GitHub Advisory
GHSA-rrfc-gjm9-cgrj

Frequently asked questions

What is CVE-2026-128086?

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.

Is CVE-2026-128086 actively exploited?

Active exploitation of CVE-2026-128086 has not been confirmed. Its EPSS score was 0.4% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-128086?

CVE-2026-128086 has a CVSS v3 base score of 5.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.

Running go.opentelemetry.io/otel/baggage? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record