Sandbox escape in vm2 via host Object exposure
CVE-2026-43997 is a critical sandbox escape vulnerability in the vm2 Node.js sandbox library. In vm2 versions prior to 3.11.0, code running inside the sandbox can obtain a reference to the host Object. Once the host Object is exposed, the sandbox boundary can be bypassed. The provided context notes one exploitation path using HostObject.getOwnPropertySymbols to obtain Symbol(nodejs.util.inspect.custom), and also characterizes the issue as abusing util.inspect and prototype traversal to achieve escape. Successful exploitation allows attacker-controlled code executing inside vm2 to break out of the intended isolation model.
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.
Affected products & vendors
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.
Recent activity
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 obtaining the host Object and escaping the sandbox in versions prior to 3.11.0.
A critical vm2 sandbox escape vulnerability involving util.inspect and prototype traversal.
A critical vm2 code injection vulnerability that allows obtaining the host Object, escaping the sandbox, and executing arbitrary code.
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.