Medium severity · published Jun 22, 2026
CVE-2026-54285
opentelemetry-js: Unbounded memory allocation in W3C Baggage propagation
5.3
CVSS
0.4%
EPSS
No
On KEV
Description
opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, 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. This vulnerability is fixed in 2.8.0.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
None
Availability
Low
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 34% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
OP
opentelemetry-js · open-telemetry
< 2.8.0 · source: vendor
OP
Opentelemetry · Opentelemetry
before 2.8.0 · source: NVD
Affected product
OP
opentelemetry-js
open-telemetry
More from opentelemetry-js
7.5
CVE-2026-59892
OpenTelemetry JavaScript: Denial of service in `JaegerPropagator` via unhandled exception on a malformed header
7.5
CVE-2026-44902
opentelemetry-js: Prometheus exporter process crash via malformed HTTP request