CVE-2026-44001

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4%, 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: cna:github_m, epss
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0

A fix is available — apply it.

vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, a sandbox escape vulnerability in vm2 v3.10.5 allows any sandboxed code to crash the host Node.js process via a single Promise constructor that triggers an unhandled rejection propagating to the host. The fix for CVE-2026-22709 (v3.10.2) only sanitized the onRejected callback in .then() and .catch() overrides and did not address the executor-to-unhandledRejection path. This vulnerability is fixed in 3.11.0.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
70(Attend)
EG Risk 70/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
Severity86% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

May 13, 2026

Last Modified

September 7, 2026

Advisory Details (1)

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

Sandbox Escape via Promise Constructor Unhandled Rejection (Process Crash DoS) · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-hw58-p9xv-2mjh

Vendor Advisories for CVE-2026-44001(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
vm2—3.11.0—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-44001?
CVE-2026-44001 is a high vulnerability published on May 13, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, a sandbox escape vulnerability in vm2 v3.10.5 allows any sandboxed code to crash the host Node.js process via a single Promise constructor that triggers an unhandled rejection propagating to the host. The fix for CVE-2026-22709…
When was CVE-2026-44001 disclosed?
CVE-2026-44001 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on September 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44001 actively exploited?
CVE-2026-44001 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 61.7% of all scored CVEs.
What is the CVSS score of CVE-2026-44001?
CVE-2026-44001 has a CVSS v4.0 base score of 8.6 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-44001?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44001, 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-44001

Explore →

Is Your Infrastructure Affected by CVE-2026-44001?

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

Start Free Scan →Browse All CVEs