CVE-2026-44009 is a critical sandbox escape vulnerability in vm2, the Node.js sandbox library. The issue affects vm2 versions prior to 3.11.2 and is associated with exception handling, specifically the handleException logic. Available reporting describes the flaw as involving a null-prototype exception condition that can expose host-side objects across the sandbox boundary, allowing attacker-controlled code running inside the vm2 sandbox to regain access to powerful host-language primitives such as the Function constructor. This breaks vm2’s isolation guarantees and can be leveraged to escape the sandbox and execute arbitrary code on the underlying host.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vm2 sandbox escape vulnerability mentioned only in a list/range of related historical issues.
A prior vm2 sandbox escape vulnerability listed in the security history.
A vulnerability affecting the vm2 open source vm/sandbox for Node.js prior to version 3.11.2. The content indicates high impact to confidentiality, integrity, and availability based on the listed CVSS vector.
Critical vm2 sandbox escape vulnerability in handleException that can enable remote code execution on the host environment.
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.