opentelemetry-js: Improper Handling of Exceptional Conditions
CVE-2026-44902 is a high-severity improper handling of exceptional conditions vulnerability in opentelemetry-js from Open-telemetry, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected opentelemetry-js versions: < 0.217.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.47% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Opentelemetry/auto-instrumentations-node to 0.75.0 or a later version.
- Update Opentelemetry/exporter-prometheus to 0.217.0 or a later version.
- Update Opentelemetry/sdk-node to 0.217.0 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Open-telemetry | opentelemetry-js | < 0.217.0 | Not stated |
| @opentelemetry | exporter-prometheus | < 0.217.0 | Not stated |
| @opentelemetry | sdk-node | < 0.217.0 | Not stated |
| @opentelemetry | auto-instrumentations-node | < 0.75.0 | Not stated |
| Opentelemetry | Opentelemetry/auto-instrumentations-node | before 0.75.0 | 0.75.0 |
| Opentelemetry | Opentelemetry/exporter-prometheus | before 0.217.0 | 0.217.0 |
| Opentelemetry | Opentelemetry/sdk-node | before 0.217.0 | 0.217.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (github.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Handling of Exceptional Conditions
The product does not handle or incorrectly handles an exceptional condition.
More Improper Handling of Exceptional Conditions vulnerabilities (CWE-755)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in opentelemetry-js
- 7.5 High severity
Recent Improper Handling of Exceptional Conditions vulnerabilities
- 7.3 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 7.5 High severity
Spotted an error? Tell us.