Loading vulnerability…
vm2 Promise Species Sandbox Escape
CVE-2026-24120 is a critical sandbox escape in the vm2 Node.js sandbox. It bypasses the incomplete mitigation for CVE-2023-37466 in Promise species handling. Attacker-controlled sandbox code can replace Object.defineProperty with a no-op, preventing the resetPromiseSpecies safeguard from restoring a safe Promise species. A crafted Promise chain can then expose a host-realm TypeError; traversal of that error object's constructor chain provides access to host-realm functionality and enables escape from vm2 isolation. The vulnerability affects vm2 releases prior to 3.10.5; reported affected releases include 3.10.3 and earlier.
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.
An attacker can escape the vm2 sandbox and execute arbitrary commands in the host Node.js environment. This can result in complete compromise of the host process, including execution of operating-system commands, access to files and secrets available to that process, modification of host resources, and potential service disruption. The reported CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8).
If you can’t patch tonight, do this now.
Until upgrades are complete, do not execute attacker-controlled or untrusted JavaScript using affected vm2 versions. Restrict access to code-evaluation functionality, isolate execution workloads from sensitive host resources and credentials, and use process- or VM-level isolation for untrusted workloads rather than relying solely on an in-process JavaScript sandbox.
Patch, then assume compromise.
Upgrade vm2 to version 3.10.5 or later, which patches this vulnerability and adds defense-in-depth protections. Audit direct and transitive dependencies to identify installations of vm2 below 3.10.5. Deploy the latest maintained vm2 release where feasible, since later releases address additional sandbox-escape vulnerabilities.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.