CVE-2026-44902

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

May 27, 2026

Last Modified

May 29, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Prometheus exporter process crash via malformed HTTP request · Advisory · open-telemetry/opentelemetry-js · GitHub

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

Vendor Advisories for CVE-2026-44902(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform/bootc-automation-portal-rhel9:17860065732026-08-06redhat
redhatrhdh/rhdh-hub-rhel9:17842109212026-07-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
npm(3)
PackageVulnerable rangeFixed inDependents
@opentelemetry/auto-instrumentations-node—0.75.0—
@opentelemetry/exporter-prometheus—0.217.0—
@opentelemetry/sdk-node—0.217.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 81× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 05:16 UTCEG score recompute
  4. 2026-08-25 05:16 UTCVendor advisory
  5. 2026-08-23 15:00 UTCEG score recompute
  6. 2026-08-23 15:00 UTCVendor advisory
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 20:34 UTCVendor advisory
  10. 2026-08-21 01:29 UTCEG score recompute
  11. 2026-08-21 01:29 UTCVendor advisory
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-20 11:18 UTCEG score recompute
  14. 2026-08-20 11:18 UTCVendor advisory
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 09:16 UTCVendor advisory
  19. 2026-08-16 15:14 UTCEG score recompute
  20. 2026-08-16 15:14 UTCVendor advisory
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:49 UTCEG score recompute
  23. 2026-08-16 02:49 UTCVendor advisory
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:55 UTCEG score recompute
Show 75 more
  1. 2026-08-15 01:55 UTCVendor advisory
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 13:41 UTCVendor advisory
  4. 2026-08-14 01:26 UTCEG score recompute
  5. 2026-08-14 01:26 UTCVendor advisory
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 02:21 UTCVendor advisory
  8. 2026-08-12 14:07 UTCEG score recompute
  9. 2026-08-12 14:07 UTCVendor advisory
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 01:49 UTCEG score recompute
  12. 2026-08-12 01:49 UTCVendor advisory
  13. 2026-08-11 13:34 UTCVendor advisory
  14. 2026-08-11 00:12 UTCEG score recompute
  15. 2026-08-11 00:12 UTCVendor advisory
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 11:13 UTCVendor advisory
  18. 2026-08-09 22:58 UTCEG score recompute
  19. 2026-08-09 22:58 UTCVendor advisory
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 10:44 UTCVendor advisory
  22. 2026-08-08 22:21 UTCEG score recompute
  23. 2026-08-08 22:21 UTCVendor advisory
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 10:04 UTCVendor advisory
  26. 2026-08-07 21:50 UTCEG score recompute
  27. 2026-08-07 21:50 UTCVendor advisory
  28. 2026-08-07 09:35 UTCVendor advisory
  29. 2026-08-06 21:21 UTCEG score recompute
  30. 2026-08-06 21:21 UTCVendor advisory
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-06 09:06 UTCVendor advisory
  33. 2026-08-05 20:52 UTCEG score recompute
  34. 2026-08-05 20:52 UTCVendor advisory
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:38 UTCEPSS rescore
  38. 2026-08-04 04:41 UTCVendor advisory
  39. 2026-08-03 16:27 UTCEG score recompute
  40. 2026-08-03 16:27 UTCVendor advisory
  41. 2026-08-03 10:36 UTCEPSS rescore
  42. 2026-08-03 03:58 UTCVendor advisory
  43. 2026-08-02 15:44 UTCVendor advisory
  44. 2026-08-02 03:29 UTCEG score recompute
  45. 2026-08-02 03:29 UTCVendor advisory
  46. 2026-08-02 02:27 UTCEPSS rescore
  47. 2026-08-01 15:14 UTCEG score recompute
  48. 2026-08-01 15:14 UTCVendor advisory
  49. 2026-08-01 04:16 UTCEPSS rescore
  50. 2026-07-31 07:29 UTCEG score recompute
  51. 2026-07-31 07:29 UTCVendor advisory
  52. 2026-07-30 16:28 UTCEPSS rescore
  53. 2026-07-30 01:30 UTCEPSS rescore
  54. 2026-07-29 15:06 UTCEG score recompute
  55. 2026-07-29 15:06 UTCVendor advisory
  56. 2026-07-28 15:36 UTCEPSS rescore
  57. 2026-07-27 14:13 UTCEPSS rescore
  58. 2026-07-27 10:11 UTCEG score recompute
  59. 2026-07-27 10:11 UTCVendor advisory
  60. 2026-07-25 14:18 UTCEPSS rescore
  61. 2026-07-24 14:17 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 03:15 UTCEG score recompute
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-21 15:24 UTCEPSS rescore
  66. 2026-07-20 17:08 UTCEPSS rescore
  67. 2026-07-19 14:31 UTCEPSS rescore
  68. 2026-07-19 02:29 UTCEPSS rescore
  69. 2026-07-18 10:04 UTCEPSS rescore
  70. 2026-07-16 17:03 UTCEPSS rescore
  71. 2026-07-15 16:57 UTCEPSS rescore
  72. 2026-07-15 02:00 UTCEPSS rescore
  73. 2026-07-13 22:30 UTCEPSS rescore
  74. 2026-07-13 06:13 UTCEPSS rescore
  75. 2026-07-12 05:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-44902?
CVE-2026-44902 is a high vulnerability published on May 27, 2026. 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…
When was CVE-2026-44902 disclosed?
CVE-2026-44902 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44902 actively exploited?
CVE-2026-44902 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.3% of all scored CVEs.
What is the CVSS score of CVE-2026-44902?
CVE-2026-44902 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44902?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44902, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44902

Explore →

Is Your Infrastructure Affected by CVE-2026-44902?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs