CVE-2026-54285
Published:June 15, 2026
Updated:June 16, 2026
Overview "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. Parsing oversized baggage causes memory allocation proportional to the header size without any cap. Impact The practical availability impact for most Node.js deployments is limited. Node.js enforces a default "--max-http-header-size" of 16,384 bytes on the total combined size of all HTTP headers, constraining what an external attacker can deliver before the propagator is reached. Additionally, the header is already in memory (parsed by the HTTP layer) by the time it reaches the propagator - the additional allocation is the overhead of splitting into entry objects, not an unbounded read. The risk is higher when transport-layer limits are absent - e.g., non-HTTP transports (messaging systems, custom "TextMapGetter" implementations) or deployments that have raised "--max-http-header-size". Remediation Update "@opentelemetry/core" to version 2.8.0 or later. The fix enforces limits consistent with the W3C Baggage specification at the propagator level: - Maximum total baggage size: 8,192 bytes - Maximum number of entries: 180 - Maximum per-entry size: 4,096 bytes Headers that exceed these limits are truncated at the point the limit is reached. Workarounds Ensure header size limits are configured at the server or gateway level. The default Node.js HTTP header limit (16 KB) mitigates external attack vectors independently of this fix. For non-HTTP transports receiving baggage from untrusted sources, validate input size before passing it to the propagator. References - "W3C Baggage Specification - Limits" (https://www.w3.org/TR/baggage/#limits) - opentelemetry-java: "GHSA-rcgg-9c38-7xpx" (https://github.com/open-telemetry/opentelemetry-java/security/advisories/GHSA-rcgg-9c38-7xpx) - opentelemetry-go: "GHSA-mh2q-q3fh-2475" (https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475) Credit Reported by tonghuaroot.
Affected Packages
https://github.com/open-telemetry/opentelemetry-js.git (GITHUB):
Affected version(s) >=v0.0.0 <v2.8.0Fix Suggestion:
Update to version v2.8.0@opentelemetry/core (NPM):
Affected version(s) >=0.1.0 <2.8.0Fix Suggestion:
Update to version 2.8.0Related Resources (2)
Do you need more information?
Contact UsCVSS v4
Base Score:
6.9
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
NONE
Vulnerable System Availability
LOW
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Weakness Type (CWE)
Allocation of Resources Without Limits or Throttling