Loading vulnerability…
CVE-2026-47210 is a critical sandbox escape vulnerability in vm2, the Node.js sandbox library, affecting versions prior to 3.11.4. When untrusted code is executed with async support on runtimes that expose WebAssembly JavaScript Promise Integration (JSPI), including WebAssembly.promising and WebAssembly.Suspending, a JSPI-backed Promise can reach Promise.prototype.finally() through a path that bypasses vm2’s expected Promise-species hardening. This allows attacker-controlled species logic to receive a host-originated rejection object, exposing host-realm behavior inside the sandbox and breaking vm2’s isolation model. The flaw stems from vm2 not anticipating this JSPI-created Promise category and therefore failing to interpose its normal bridge protections. Successful exploitation can pivot from the exposed host object to arbitrary code execution in the host process.
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.
6 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 vulnerability that abuses WebAssembly JSPI on Node.js 26 to bypass Promise hardening and achieve host process access and arbitrary command execution.
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.
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.