Loading vulnerability…
CVE-2026-47135 is a sandbox escape vulnerability in vm2, a Node.js sandbox library. In affected versions prior to 3.11.4, vm2's Symbol.for override in setup-sandbox.js blocks only a subset of dangerous Node.js cross-realm symbols, while bridge write-direction traps in bridge.js, including set, defineProperty, and deleteProperty, do not enforce dangerous-symbol checks on property keys. This combination allows untrusted code executing inside the vm2 sandbox to obtain real cross-realm symbols from the host realm and use them as property keys on host objects exposed across the sandbox boundary. By tampering with symbol-keyed host object behavior, an attacker can influence host-side control flow and semantics. Exploitation was verified through a util.promisify hijack chain, demonstrating that sandboxed code can manipulate host behavior despite vm2's intended isolation. The issue undermines the sandbox boundary but is described as not being a direct remote code execution vulnerability by itself.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vm2 sandbox escape / host behavior control vulnerability in Node.js environments caused by incomplete interception of dangerous cross-realm symbols and missing safety checks in bridge property traps.
A sandbox escape vulnerability in the vm2 Node.js library caused by incomplete blocking of dangerous cross-realm Symbol.for keys and missing symbol checks in bridge write traps, enabling host-side behavior hijacking.
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.