Resource exhaustion in Open-Telemetry Opentelemetry-Js
CVE-2026-54285
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
EPSS exploit prediction
EPSS: 0.004 (31.9th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 32nd percentile — 31.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.004 · change: +0.001
Affected products
- Open-Telemetry Opentelemetry-Js — versions < 2.8.0
- Opentelemetry
Weakness classification (CWE)
References
- github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-8988-4f7v-9… (Mitigation, Vendor Advisory)
Frequently asked questions
- What is CVE-2026-54285?
- CVE-2026-54285 is a medium-severity vulnerability in Open-Telemetry Opentelemetry-Js, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 5.3/10. Published 2026-06-22.
- How severe is CVE-2026-54285?
- Medium severity. CVSS v3 base score is 5.3 out of 10.