CVE-2026-54285: opentelemetry-js: Unbounded memory allocation in W3C Baggage propagation
open-telemetry · opentelemetry-js
Affected: open-telemetry opentelemetry-js · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 35% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- open-telemetry · opentelemetry-js< 2.8.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- open-telemetry
- Published
- June 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-54285 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.