Loading vulnerability…
CVE-2026-22709 is a sandbox escape vulnerability in the vm2 Node.js library affecting versions before 3.10.2. In lib/setup-sandbox.js, vm2 sanitizes callbacks for local Promise methods but does not properly sanitize callbacks associated with global Promise objects returned by async functions. The vulnerable global Promise then and catch implementations use Function.prototype.call, which attacker-controlled code can intercept to bypass callback sanitization. This can expose host-realm objects to sandboxed code, enabling escape from the vm2 boundary and arbitrary code execution in the host Node.js environment.
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.
63 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previous vm2 Promise callback-sanitization bypass referenced for comparison; it is not the same root cause as CVE-2026-92944.
A vm2 sandbox-escape vulnerability affecting Flowise's outdated nodevm fork and allowing remote code execution in Flowise 3.1.1.
Related vm2 vulnerability mentioned as another example of the same root weakness class affecting dynamically managed code resources.
A prior critical vm2 sandbox escape vulnerability described as a Promise callback bypass, mentioned for comparison as part of a broader wave of vm2 flaws.
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.