CVE-2026-44007 is an improper access control vulnerability in the vm2 sandbox library for Node.js affecting versions prior to 3.11.1. When a NodeVM instance is created with nesting enabled, sandboxed code can import the vm2 package regardless of the outer VM's module loading restrictions, including configurations intended to disable require entirely. By obtaining access to vm2 from inside the sandbox, an attacker can instantiate a nested NodeVM with attacker-controlled require settings and use that inner VM to break isolation and execute commands on the underlying host. The flaw effectively turns the nesting feature into a sandbox escape path for applications that execute untrusted JavaScript in a NodeVM with nesting enabled.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vm2 sandbox escape CVE mentioned only as part of a historical list.
A prior vm2 sandbox escape vulnerability listed in the security history.
A prior vm2 sandbox escape vulnerability mentioned in the vendor security history table.
A sandbox escape in vm2 for Node.js that allows arbitrary OS command execution on the host when NodeVM is created with nesting: true, leading to full compromise of applications running untrusted code.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.