npm package report

Is @opentelemetry/propagator-jaeger safe?

1 known vulnerability, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
0.80%

chance of exploitation in the next 30 days

xyz score
4.1

CyberXYZ composite, out of 10

fig. 01 — GHSA-45rx-2jwx-cxfr, the advisory selected below

// advisories

GHSA-45rx-2jwx-cxfr

HIGHCVE-2026-59892

@opentelemetry/propagator-jaeger decodes incoming HTTP header values with decodeURIComponent() without handling decode errors. A single request carrying a malformed percent-encoded value (for example a bare %) in an uber-trace-id or uberctx- header throws an uncaught URIError, terminating any Node.js process that uses JaegerPropagator as its active propagator.

Affected
< 2.9.0
Fixed in
2.9.0
Weakness
CWE-248
Published
2026-07-21
Source
github

GHSANVDMITREreferencereferencereference

// 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 01:45 UTC. The most recent advisory here was published 2026-07-21. 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/propagator-jaeger safe? npm package security report | CyberXYZ