vm2 sandbox escape via JSPI-backed Promise.finally() species bypass
CVE-2026-47210 is a sandbox escape vulnerability in vm2, the Node.js sandbox library, affecting versions prior to 3.11.4. When vm2 executes untrusted code with async support on runtimes that expose WebAssembly JavaScript Promise Integration (JSPI) features such as WebAssembly.promising or WebAssembly.Suspending, a JSPI-backed Promise can reach the global Promise.prototype.finally() path in a way that bypasses vm2's expected Promise-species hardening. In the described scenario, this bypass exposes a host-originated rejection object to attacker-controlled species logic, breaking the intended sandbox boundary and enabling execution of attacker-controlled code in the host process.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A sandbox escape vulnerability in vm2 for Node.js that allows arbitrary code execution in the host process under specific async and WebAssembly JSPI runtime conditions.
A critical vm2 sandbox escape affecting asynchronous environments with JSPI support, where Promise.finally species handling can expose host-originated error objects and lead to host RCE.
The version that knows your 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.