opentelemetry_sdk
Affected
- introduced
0, fixed0.32.1(semver)
Fixed versions
0.32.1
Fix
- Fixed version
0.32.1cargo update -p opentelemetry_sdk --precise 0.32.1
Advisory
Also known as: CVE-2026-48504
opentelemetry_sdk has unbounded memory allocation in W3C Baggage propagation
Summary
BaggagePropagator::extract_with_context in opentelemetry_sdk did not enforce the W3C Baggage size limits before parsing an inbound baggage header. A large attacker-controlled header could cause unnecessary CPU work and short-lived heap allocations while parsing entries that would later be discarded by the SDK's baggage storage limits.
The SDK now applies limits aligned with the W3C Baggage limits:
Impact
Services that accept untrusted inbound propagation headers may experience increased per-request resource usage when processing oversized baggage headers. This can contribute to denial-of-service risk, especially when application or transport-level header limits are absent or configured above the W3C Baggage limits.
The impact is limited to availability. This issue does not expose telemetry data, modify telemetry data, or allow code execution.
Patches
Upgrade opentelemetry_sdk to version 0.32.1 or later.
Version 0.32.1 rejects baggage header values larger than 8192 bytes and limits extraction to the first 64 list-members.
## Workarounds
If upgrading immediately is not possible, reject or limit inbound baggage headers larger than 8192 bytes before invoking OpenTelemetry propagation extraction. This can be enforced at a proxy, gateway, middleware layer, or custom carrier boundary.
Resources
Credit
tonghuaroot
Medium Basis: The source's own band: MODERATE
0, fixed 0.32.1 (semver)0.32.1
0.32.1cargo update -p opentelemetry_sdk --precise 0.32.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0