Is CVE-2026-44902 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44902 being exploited in the wild.

How severe is CVE-2026-44902?

High severity, with a CVSS score of 7.5, published 27 May 2026.

Which products and versions are affected?

@opentelemetry/auto-instrumentations-node (npm) < 0.75.0, SEMVER:introduced=0,fixed=0.75.0; @opentelemetry/exporter-prometheus (npm) < 0.217.0, SEMVER:introduced=0,fixed=0.217.0; @opentelemetry/sdk-node (npm) < 0.217.0, SEMVER:introduced=0,fixed=0.217.0.

Is there a fix for CVE-2026-44902?

Yes. @opentelemetry/auto-instrumentations-node (npm): upgrade to 0.75.0 or later; @opentelemetry/exporter-prometheus (npm): upgrade to 0.217.0 or later; @opentelemetry/sdk-node (npm): upgrade to 0.217.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44902 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-44902?

Check whether you run @opentelemetry/auto-instrumentations-node (npm), @opentelemetry/exporter-prometheus (npm), @opentelemetry/sdk-node (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44902: OpenTelemetry opentelemetry-js denial of service in Prometheus exporter

Q: Is there a fix for CVE-2026-44902?

Yes. @opentelemetry/auto-instrumentations-node (npm): upgrade to 0.75.0 or later; @opentelemetry/exporter-prometheus (npm): upgrade to 0.217.0 or later; @opentelemetry/sdk-node (npm): upgrade to 0.217.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-44902 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-44902?

Check whether you run @opentelemetry/auto-instrumentations-node (npm), @opentelemetry/exporter-prometheus (npm), @opentelemetry/sdk-node (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44902 · Severity: high · CVSS 7.5 · Published 2026-05-27

A vulnerability in the OpenTelemetry Prometheus exporter for Node.js allows an unauthenticated attacker to crash the entire application process. By sending a single specially crafted web request to the metrics endpoint, an attacker can trigger a fatal error that shuts down the service. This results in a complete denial of service for any application using this monitoring component.

Vendors: npm, Opentelemetry.

Quick answers

Is CVE-2026-44902 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44902 being exploited in the wild.
How severe is CVE-2026-44902?: High severity, with a CVSS score of 7.5, published 27 May 2026.
Which products and versions are affected?: @opentelemetry/auto-instrumentations-node (npm) < 0.75.0, SEMVER:introduced=0,fixed=0.75.0; @opentelemetry/exporter-prometheus (npm) < 0.217.0, SEMVER:introduced=0,fixed=0.217.0; @opentelemetry/sdk-node (npm) < 0.217.0, SEMVER:introduced=0,fixed=0.217.0.
Is there a fix for CVE-2026-44902?: Yes. @opentelemetry/auto-instrumentations-node (npm): upgrade to 0.75.0 or later; @opentelemetry/exporter-prometheus (npm): upgrade to 0.217.0 or later; @opentelemetry/sdk-node (npm): upgrade to 0.217.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44902 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-44902?: Check whether you run @opentelemetry/auto-instrumentations-node (npm), @opentelemetry/exporter-prometheus (npm), @opentelemetry/sdk-node (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@opentelemetry/auto-instrumentations-node (npm): upgrade to 0.75.0 or later
```
npm install @opentelemetry/auto-instrumentations-node@0.75.0
```
@opentelemetry/exporter-prometheus (npm): upgrade to 0.217.0 or later
```
npm install @opentelemetry/exporter-prometheus@0.217.0
```
@opentelemetry/sdk-node (npm): upgrade to 0.217.0 or later
```
npm install @opentelemetry/sdk-node@0.217.0
```

Technical details

The vulnerability is an unhandled exception (TypeError) in the `_requestHandler` of `PrometheusExporter.ts`. When the exporter's built-in HTTP server receives a malformed absolute-form URI (e.g., 'http://'), the `new URL()` constructor throws an 'Invalid URL' error. Because this call is not wrapped in a try-catch block, the exception propagates to the top level, causing the Node.js process to terminate. This can be exploited by an unauthenticated remote attacker with network access to the metrics port (default 9464). Patches are available in @opentelemetry/exporter-prometheus v0.217.0 and @opentelemetry/auto-instrumentations-node v0.75.0.

Affected products

OpenTelemetry @opentelemetry/exporter-prometheus < 0.217.0
OpenTelemetry @opentelemetry/sdk-node < 0.217.0
OpenTelemetry @opentelemetry/auto-instrumentations-node < 0.75.0

Identifiers

CVE-2026-44902
GHSA-q7rr-3cgh-j5r3

Timeline

2026-05-11: advisory: GitHub Advisory published
2026-05-27: other: NVD published date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.