Description
W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path.
Recommendation
Update the @opentelemetry/core package to the latest compatible version. Followings are version details:
- Affected version(s): < 2.8.0
- Patched version(s): 2.8.0
References
Could your website be exposed too?
SmartScanner can check your website for OpenTelemetry Core: Unbounded memory allocation in W3C Baggage propagation and gives you actionable findings to investigate.
Start a free scanRelated Issues
- Browserslist: Unbounded memory growth (no cache eviction) via distinct query results, leading to eventual OOM - CVE-2026-73089
- Uncontrolled memory allocation via crafted SVG dimensions in @dicebear/converter - CVE-2026-29112
- LiquidJS has a memory and render limit bypass via unbounded width padding in `date` filter (strftime) - CVE-2026-45357
- Malware in @tanstack/* packages exfiltrates cloud credentials, GitHub tokens, and SSH keys - @tanstack/router-core - CVE-2026-45321


