Loading vulnerability…
CVE-2026-44006 is a critical sandbox-escape vulnerability in vm2, an open-source sandbox library for Node.js. In versions prior to 3.11.0, attacker-controlled code running inside the vm2 sandbox can reach the BaseHandler.getPrototypeOf path and use it to obtain arbitrary prototypes from the host context. This breaks the intended isolation boundary between sandboxed and host objects by exposing host-side prototype references that should remain inaccessible or be safely proxied. Because vm2 relies on JavaScript-level proxying and object mediation to enforce isolation, access to arbitrary host prototypes can be leveraged to traverse into host objects and ultimately escape the sandbox. The issue is fixed in vm2 3.11.0.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Critical vm2 sandbox escape / remote code execution vulnerability where sandbox code reaches BaseHandler.getPrototypeOf and gains access to arbitrary host-context prototypes, bypassing proxy isolation.
A prior vm2 sandbox escape vulnerability via getPrototypeOf injection, mentioned as historical context.
A vm2 sandbox escape CVE mentioned only as part of a historical list.
A prior vm2 sandbox escape vulnerability listed in the security history.
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.