Answer in brief
CVE-2026-128086 records a Medium severity (CVSS 5.3) vulnerability in OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification. The current sources do not mark it as known exploited. The current feed maps open-telemetry/opentelemetry-go (generic), go.opentelemetry.io/otel/baggage (go), go.opentelemetry.io/otel/baggage (go), go.opentelemetry.io/otel/propagation (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps open-telemetry/opentelemetry-go (generic), go.opentelemetry.io/otel/baggage (go), go.opentelemetry.io/otel/baggage (go), go.opentelemetry.io/otel/propagation (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| open-telemetry/opentelemetry-gogeneric | >=1.0.0-RC1 <1.47.0 | 1.47.0 |
| go.opentelemetry.io/otel/baggagego | >=1.0.0-RC1,<1.47.0 | 1.47.0 |
| go.opentelemetry.io/otel/baggagego | >=1.0.0-RC1 <1.47.0 | 1.47.0 |
| go.opentelemetry.io/otel/propagationgo | >=1.0.0-RC1,<1.47.0 | 1.47.0 |
| go.opentelemetry.io/otel/propagationgo | >=1.0.0-RC1 <1.47.0 | 1.47.0 |
Published upstream
Nov 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 13, 2026
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.
Quoted source text, attributed separately from HOL analysis.