Loading vulnerability…
vm2 BaseHandler.getPrototypeOf Sandbox Escape
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can allow sandbox escape from untrusted JavaScript executed inside vm2 into the surrounding host Node.js context. The resulting impact can include arbitrary code execution on the host, compromise of confidentiality, integrity, and availability, and full defeat of the sandbox security boundary. In deployments that expose vm2 to remote attacker-supplied code, this can amount to unauthenticated remote code execution in the host process.
If you can’t patch tonight, do this now.
Until patched, avoid executing untrusted or attacker-controlled JavaScript with affected vm2 versions. Reduce exposure by disabling or isolating features and services that accept arbitrary code for vm2 execution, placing execution behind stronger process-, container-, or VM-level isolation boundaries, and restricting the privileges of the host process to limit post-escape impact. Where feasible, migrate away from vm2 for high-risk multi-tenant or adversarial code-execution use cases.
Patch, then assume compromise.
Upgrade vm2 to version 3.11.0 or later. Broader reporting around the 2026 vm2 vulnerability cluster recommends moving to the latest available fixed release in the 3.11.x line, such as 3.11.2 or later where applicable, to pick up additional sandbox-escape fixes beyond this CVE. If vm2 is used for execution of untrusted code in production, evaluate replacing it with stronger isolation mechanisms because the project has a recurring history of critical sandbox escapes.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.