CVE-2026-44007

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 41% 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, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.1, when a NodeVM is created with nesting: true, sandbox code can unconditionally require('vm2') regardless of the outer VM's require configuration — including require: false. With access to vm2, the sandbox constructs a new inner NodeVM with its own unrestricted require settings and executes arbitrary OS commands on the host. Any application that runs untrusted code inside a NodeVM with nesting: true is fully compromised. This vulnerability is fixed in 3.11.1.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track*)
EG Risk 57/100SSVC: Track*

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
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
60%
KEV
Not listed

Published

May 13, 2026

Last Modified

September 7, 2026

Advisory Details (6)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44007.json
redhat

2477198 – (CVE-2026-44007) CVE-2026-44007 vm2: vm2: Arbitrary code execution via nested NodeVM bypass

https://bugzilla.redhat.com/show_bug.cgi?id=2477198
redhat Patch Available

CVE-2026-44007 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-44007
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:50850
generic

oss-security - vm2: sandbox escape in NodeVM with nesting:true (CVE-2026-44007)

http://www.openwall.com/lists/oss-security/2026/05/05/11
github Patch Available🟡 PoC Available

nesting: true bypasses require: false, allowing sandbox escape to arbitrary OS command execution · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-8hg8-63c5-gwmx

Vendor Advisories for CVE-2026-44007(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.1—

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44007?
CVE-2026-44007 is a critical vulnerability published on May 13, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.1, when a NodeVM is created with nesting: true, sandbox code can unconditionally require('vm2') regardless of the outer VM's require configuration — including require: false. With access to vm2, the sandbox constructs a new inner NodeVM…
When was CVE-2026-44007 disclosed?
CVE-2026-44007 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-44007 actively exploited?
CVE-2026-44007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 40.0% of all scored CVEs.
What is the CVSS score of CVE-2026-44007?
CVE-2026-44007 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-44007?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44007, 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-44007

Explore →

Is Your Infrastructure Affected by CVE-2026-44007?

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

Start Free Scan →Browse All CVEs