Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-44902: opentelemetry-js is the OpenTelemetry JavaScript Client

46
This week
HIGH 7.5REMOTEUPGRADEUPGRADEUPGRADE

CVE-2026-44902 is a high-severity flaw (CVSS 7.5) affecting opentelemetry\/auto-instrumentations-node, opentelemetry\/exporter-prometheus, opentelemetry\/sdk-node. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 0.217.0, a single malformed HTTP request crashes any Node.js process running the OpenTelemetry JS Prometheus exporter. The metrics endpoint (default 0.0.0.0:9464) has no error handling around URL parsing, so a request with an invalid URI causes an uncaught TypeError that terminates the process. This vulnerability is fixed in 0.217.0.

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 59%)
CISA exploited listNo
WeaknessCWE-755
Published2026-05-27
Last modified2026-08-27
Publisher (CNA): GitHub, Inc. · Vendor: opentelemetry

Share: LinkedIn · X · Reddit

Last updated 2026-08-27 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

opentelemetry opentelemetry\/auto-instrumentations-node UPGRADE
Affected: < 0.75.0
Fixed in: 0.75.0
Safe to downgrade to: no unaffected older release
1. Check installed version
npm ls opentelemetryauto-instrumentations-node
2. UPGRADE to 0.75.0
npm install opentelemetryauto-instrumentations-node@">=0.75.0"
opentelemetry opentelemetry\/exporter-prometheus UPGRADE
Affected: < 0.217.0
Fixed in: 0.217.0
Safe to downgrade to: no unaffected older release
1. Check installed version
npm ls opentelemetryexporter-prometheus
2. UPGRADE to 0.217.0
npm install opentelemetryexporter-prometheus@">=0.217.0"
opentelemetry opentelemetry\/sdk-node UPGRADE
Affected: < 0.217.0
Fixed in: 0.217.0
Safe to downgrade to: no unaffected older release
1. Check installed version
npm ls opentelemetrysdk-node
2. UPGRADE to 0.217.0
npm install opentelemetrysdk-node@">=0.217.0"
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44902?

opentelemetry\/auto-instrumentations-node: upgrade to 0.75.0; opentelemetry\/exporter-prometheus: upgrade to 0.217.0; opentelemetry\/sdk-node: upgrade to 0.217.0. Exact commands for each OS are on this page.

Is CVE-2026-44902 being exploited?

CVE-2026-44902 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44902 affect?

CVE-2026-44902 affects opentelemetry\/auto-instrumentations-node, opentelemetry\/exporter-prometheus, opentelemetry\/sdk-node. Severity is high (CVSS 7.5). opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 0.217.0, a single malformed HTTP request crashes any Node.js process running the OpenTelemetry JS Prometheus exporter. The metrics endpoint (default 0.0.0.0:9464) has no erro

How urgent is CVE-2026-44902?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities · Prometheus vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.