CVE-2026-44902GHSA-Q7RR-3CGH-J5R3
opentelemetry-js: Prometheus exporter process crash via malformed HTTP request
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.217.0, 0.75.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- open-telemetry opentelemetry-js
fixed in 0.217.0
- @opentelemetry exporter-prometheus
fixed in 0.217.0
- @opentelemetry sdk-node
fixed in 0.217.0
- @opentelemetry auto-instrumentations-node
fixed in 0.75.0
- @opentelemetry/exporter-prometheusnpm
fixed in 0.217.0
- @opentelemetry/sdk-nodenpm
From 0.57.0 · fixed in 0.217.0
- @opentelemetry/auto-instrumentations-nodenpm
From 0.55.0 · fixed in 0.75.0