npm package report

Is @opentelemetry/core safe?

1 known vulnerability, worst severity MODERATE.

cvss
5.3

how bad it is if exploited, out of 10

epss
0.30%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-8988-4f7v-96qf, the advisory selected below

// advisories

GHSA-8988-4f7v-96qf

MODERATECVE-2026-54285

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 withou

Affected
< 2.8.0, >=0, <2.8.0
Fixed in
2.8.0
Weakness
CWE-770
Published
2026-06-15
Source
github

GHSANVDMITREreference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 03:44 UTC. The most recent advisory here was published 2026-06-15. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @opentelemetry/core safe? npm package security report | CyberXYZ