Vulnerability in @opentelemetry/exporter-prometheus (CVE-2026-44902)
Summary
Vulnerability in @opentelemetry/exporter-prometheus (CVE-2026-44902). Risk of unauthorized operations or information disclosure. Exploitable via TypeError. Mitigation: upgrade to 0.217.0 or later.
Original description
The description as published by the source.
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: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44902 has been found in @opentelemetry/exporter-prometheus.
Attackers can target a specific entry point like TypeError over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade @opentelemetry/exporter-prometheus to 0.217.0 or later.
If unsure, ask your IT team or search "@opentelemetry/exporter-prometheus CVE-2026-44902" on the vendor's site.
CVE-2026-44902 (@opentelemetry/exporter-prometheus) — CWE-755 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: TypeError / OTEL_METRICS_EXPORTER / prometheus / host
Patched: 0.217.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-755) exists in @opentelemetry/exporter-prometheus. Attackers reach the vulnerable code path via TypeError without authentication.
Check the vendor advisory for the affected versions of @opentelemetry/exporter-prometheus. Attack surface: TypeError / OTEL_METRICS_EXPORTER / prometheus / host.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.217.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@opentelemetry/exporter-prometheus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@opentelemetry/exporter-prometheus' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@opentelemetry/exporter-prometheusを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @opentelemetry/exporter-prometheus to 0.217.0ステージング環境で 0.217.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com