CLSA-2026-1791413854 TuxCare security update for @opentelemetry/core (1 CVE)

TuxCare rebuilt @opentelemetry/core to address 1 CVE. Fixed in 1.17.1-tuxcare.1...

CLSA-2026-1791413402 TuxCare security update for @opentelemetry/core (1 CVE)

TuxCare rebuilt @opentelemetry/core to address 1 CVE. Fixed in 1.30.1-tuxcare.1...

CLSA-2026-1791409515 TuxCare security update for @opentelemetry/core (1 CVE)

TuxCare rebuilt @opentelemetry/core to address 1 CVE. Fixed in 1.22.0-tuxcare.1...

CLSA-2026-1791404287 TuxCare security update for @opentelemetry/core (1 CVE)

TuxCare rebuilt @opentelemetry/core to address 1 CVE. Fixed in 2.1.0-tuxcare.1...

Security Bulletin: Vulnerability in @opentelemetry/core affects DB2 Dev Extension (CVE-2026-54285)

Summary Upgraded @opentelemetry/core to 2.8.0. Vulnerability Details CVEID:CVE-2026-54285 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 header...

ROOT-APP-NPM-CVE-2026-54285 CVE-2026-54285 in @opentelemetry/core - Patched by Root

Root has patched CVE-2026-54285 in the @opentelemetry/core package for Root:npm. Multiple fixed versions available...

CVE-2026-54285

A flaw was found in the @opentelemetry/core component of the OpenTelemetry JavaScript Client. This vulnerability allows a remote attacker to trigger uncontrolled memory allocation by sending oversized baggage HTTP headers. The system's inability to enforce size limits during inbound baggage parsi...

GHSA-8988-4F7V-96QF OpenTelemetry Core: Unbounded memory allocation in W3C Baggage propagation

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

Allocation of Resources Without Limits or Throttling

Overview @opentelemetry/core is an OpenTelemetry Core provides constants and utilities shared by all OpenTelemetry SDK packages. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the extract function. An attacker can cause excessive memory...

0perator (>=0.1.0, <=0.3.0), @0byte/oc_mlflow_plugin (>=0.1.1, <=0.1.3) +4015 more potentially affected by CVE-2026-54285 via @opentelemetry/core (>=2.0.0, <=2.7.1)

@opentelemetry/core NPM version =2.0.0, =0.1.0, =0.1.1, =0.0.1, =1.3.0, =0.1.0, =1.2.2, =0.1.0, =0.1.0, =0.1.0, =0.1.0, =0.1.0, =0.8.0, =0.1.1, =0.1.1, =0.1.23 and more Source cves: CVE-2026-54285 Source advisory: SNYK:JS-OPENTELEMETRYCORE-17373280...

0perator (>=0.1.0, <=0.3.0), @0byte/oc_mlflow_plugin (>=0.1.1, <=0.1.3) +4015 more potentially affected by CVE-2026-54285 via @opentelemetry/core (>=2.0.0, <=2.7.1)

@opentelemetry/core NPM version =2.0.0, =0.1.0, =0.1.1, =0.0.1, =1.3.0, =0.1.0, =1.2.2, =0.1.0, =0.1.0, =0.1.0, =0.1.0, =0.1.0, =0.8.0, =0.1.1, =0.1.1, =0.1.23 and more Source cves: CVE-2026-54285 Source advisory: OSV:GHSA-8988-4F7V-96QF...

OpenTelemetry Core: Unbounded memory allocation in W3C Baggage propagation

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