Description
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.
Affected products
vm2_project: vm2
References10
- github.com/patriksimek/vm2/security/advisories/GHSA-8hg8-63c5-g… ExploitVendor Advisory
- www.openwall.com/lists/oss-security/2026/05/05/11 Mailing ListThird Party Advisory
- access.redhat.com/errata/RHSA-2026:50850
- access.redhat.com/security/cve/CVE-2026-44007
- bugzilla.redhat.com/show_bug.cgi?id=2477198
- github.com/patriksimek/vm2/commit/46cbbdde4e19b743974c942278080…
- github.com/patriksimek/vm2/releases/tag/v3.11.1
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44007…
- www.openwall.com/lists/oss-security/2026/05/05/11 Mailing ListThird Party Advisory
- access.redhat.com/errata/RHSA-2026:50850
Metrics
- CVSS 3.1
-
9.1
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 64 · as of 14 November 2026
- CWE
- CWE-284CWE-1100
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.