How severe is CVE-2026-44902?

CVE-2026-44902 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-44902?

CVE-2026-44902 affects the following packages: @opentelemetry/exporter-prometheus (npm), @opentelemetry/sdk-node (npm), @opentelemetry/auto-instrumentations-node (npm). Ecosystems affected: npm.

How do I fix CVE-2026-44902?

Update @opentelemetry/exporter-prometheus to 0.217.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44902 is resolved across your whole dependency graph.

How do I detect CVE-2026-44902 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @opentelemetry/exporter-prometheus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-44902 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-44902?

O3 pinpoints whether CVE-2026-44902 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-44902 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-44902 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2026-44902 published, and has it been updated?

CVE-2026-44902 was published on May 27, 2026 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2026-44902

HIGH

CVE-2026-44902 is a high-severity (CVSS 7.5) vulnerability in @opentelemetry/exporter-prometheus. O3 Security confirms whether CVE-2026-44902 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

opentelemetry-js: Prometheus exporter process crash via malformed HTTP request

Also known asGHSA-q7rr-3cgh-j5r3

Published

May 27, 2026

Updated

Aug 7, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Aug 7, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@opentelemetry/exporter-prometheusnpm

15.5Mdownloads / week

@opentelemetry/sdk-nodenpm

16.4Mdownloads / week

@opentelemetry/auto-instrumentations-nodenpm

7.9Mdownloads / week

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@opentelemetry/exporter-prometheus`	all versions	0.217.0
📦npm	`@opentelemetry/sdk-node`	all versions	0.217.0
📦npm	`@opentelemetry/auto-instrumentations-node`	all versions	0.75.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @opentelemetry/exporter-prometheus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @opentelemetry/exporter-prometheus to 0.217.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44902 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-44902 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-44902. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-44902 in your dependencies?

O3 detects CVE-2026-44902 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works