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 61% 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
Elevated
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.5%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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%
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

Published

May 27, 2026

Last Modified

August 27, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
@opentelemetry/auto-instrumentations-node—
  • every version up to 0.75.0: fixed in 0.75.0
—
@opentelemetry/exporter-prometheus—
  • every version up to 0.217.0: fixed in 0.217.0
—
@opentelemetry/sdk-node—
  • every version up to 0.217.0: fixed in 0.217.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 25× 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 199 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 on May 27, 2026, with the most recent update on August 27, 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.5% probability of exploitation in the next 30 days (40th percentile of EPSS-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?
A fix for CVE-2026-44902 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44902 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs