PT-2026-49598

CVE-2026-54285

·

Published

2026-06-15

·

Updated

2026-10-30

Description by

CVSS 3.1
5.3
Medium
MetricsAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Name of the Vulnerable Software and Affected Versions @opentelemetry/core versions prior to 2.8.0
Description The W3CBaggagePropagator.extract() function in @opentelemetry/core fails to enforce size limits when parsing inbound baggage HTTP headers. While the W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries, these limits were only applied to the outbound inject() path. Consequently, parsing oversized baggage leads to memory allocation proportional to the header size. The risk is increased in deployments where transport-layer limits are absent, such as non-HTTP transports, custom TextMapGetter implementations, or environments where the Node.js --max-http-header-size has been increased.
Recommendations Update to version 2.8.0 or later. Ensure header size limits are configured at the server or gateway level. For non-HTTP transports receiving baggage from untrusted sources, validate input size before passing it to the propagator.
Exploitability
Exploit
Fix
Impacts
Researchers
Vendors
Affected products
Related identifiers
GHSA-8988-4F7V-96QF
CLEANSTART-2026-DZ53181
CLEANSTART-2026-VP69884
CLEANSTART-2026-YW31790
ECHO-0B54-337C-5581
Found an issue in the description? Have something to add? Feel free to write us 👾