How severe is CVE-2026-44902?

CVE-2026-44902 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-44902 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (40th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-44902?

CVE-2026-44902 primarily affects Opentelemetry Opentelemetry/auto-instrumentations-node. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-44902?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-44902 have an EU (EUVD) identifier?

Yes. CVE-2026-44902 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-32538.

When was CVE-2026-44902 published?

CVE-2026-44902 was published on 2026-05-27 and last updated on 2026-08-27.

CVE-2026-44902

CVE-2026-44902 is a high-severity vulnerability in Opentelemetry Opentelemetry/auto-instrumentations-node with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-755.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (40th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-32538
Weakness: CWE-755
Affected product: Opentelemetry Opentelemetry/auto-instrumentations-node
Published: 2026-05-27
Last modified: 2026-08-27

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.

Frequently asked questions

What is CVE-2026-44902?: 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.
How severe is CVE-2026-44902?: CVE-2026-44902 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-44902 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (40th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-44902?: CVE-2026-44902 primarily affects Opentelemetry Opentelemetry/auto-instrumentations-node. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-44902?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-44902 have an EU (EUVD) identifier?: Yes. CVE-2026-44902 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-32538.
When was CVE-2026-44902 published?: CVE-2026-44902 was published on 2026-05-27 and last updated on 2026-08-27.

References

https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-q7rr-3cgh-j5r3

Affected products (3)

cpe:2.3:a:opentelemetry:opentelemetry\/auto-instrumentations-node:*:*:*:*:*:node.js:*:*
cpe:2.3:a:opentelemetry:opentelemetry\/exporter-prometheus:*:*:*:*:*:node.js:*:*
cpe:2.3:a:opentelemetry:opentelemetry\/sdk-node:*:*:*:*:*:node.js:*:*

Other CWE-755 (Improper Handling of Exceptional Conditions) vulnerabilities

CVE-2025-34193 — Critical (CVSS 9.8): Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 25.1.102 and Application versions prior…
CVE-2025-10156 — Critical (CVSS 9.8): An Improper Handling of Exceptional Conditions vulnerability in the ZIP archive scanning component of mmaitre314…
CVE-2022-48673 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: net/smc: Fix possible access to freed memory in…
CVE-2024-26584 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: net: tls: handle backlogging of crypto…
CVE-2021-42142 — Critical (CVSS 9.8): An issue was discovered in Contiki-NG tinyDTLS through master branch 53a0d97. DTLS servers mishandle the early use of a…
CVE-2021-42141 — Critical (CVSS 9.8): An issue was discovered in Contiki-NG tinyDTLS through 2018-08-30. One incorrect handshake could complete with…

Browse all CWE-755 (Improper Handling of Exceptional Conditions) vulnerabilities →