Loading vulnerability…
vm2 versions before 3.9.6 contain a sandbox-bypass flaw in error stack-trace generation. Sandbox-controlled code can obtain direct references to host Error objects created by Node.js internals while a stack trace is generated. These foreign host references can be used to escape the intended vm2 isolation boundary and execute arbitrary JavaScript in the host context.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An earlier vm2 sandbox escape-related vulnerability in which accessing the stack property on error objects leaks foreign references into the sandbox.
A vm2 sandbox-bypass vulnerability fixed in the Red Hat Advanced Cluster Management for Kubernetes 2.4.4 container images.
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.