Vulnerability · Published Jun 22, 2026 · Assigned by GitHub_M

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

Medium 5.3

In plain English

A medium-severity resource allocation without limits in opentelemetry-js from open-telemetry. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 35% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.3Medium

Exploit odds (30 days)0.4%top 65.3% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

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

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	@opentelemetry/core	2.8.0	GHSA-8988-4f7v-96qf

Affected products (as reported)

Vendor	Product	Versions
open-telemetry	opentelemetry-js	< 2.8.0

Weakness: CWE-770 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

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