CVE-2026-54285mediumCWE-770

CVE-2026-54285: fallo de gravedad media en open-telemetry opentelemetry-js

opentelemetry-js: Unbounded memory allocation in W3C Baggage propagation

Publicada el · Actualizada el

Seguir esta CVE+ Monitorear opentelemetry-js+ Monitorear @opentelemetry/core

Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.

13Vexday Risk Score

Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.

ssvc Trackcvss 5.3epss 0.4%
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Productos afectados
open-telemetry · opentelemetry-js
CVEs relacionadas — open-telemetry opentelemetry-js

En el mismo producto, de las más peligrosas a las menos.

CVE-2026-59892HIGHOpenTelemetry JavaScript: Denial of service in `JaegerPropagator` via unhandled exception on a malformed headerEPSS 0.6%CVE-2026-44902HIGHopentelemetry-js: Prometheus exporter process crash via malformed HTTP requestEPSS 0.5%