Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Sandbox escape in vm2 Promise callback sanitization

IdentifiersCVE-2026-22709CWE-693· Protection Mechanism Failure

CVE-2026-22709 is a critical sandbox escape vulnerability in the vm2 Node.js sandbox library. In vm2 prior to 3.10.2, Promise callback sanitization can be bypassed because vm2 sanitizes callbacks on its local Promise handling path but does not correctly sanitize the global Promise path used by async functions. Specifically, in lib/setup-sandbox.js, localPromise.prototype.then is sanitized, while globalPromise.prototype.then/.catch handling is insufficient; async functions return globalPromise objects, creating a path where attacker-controlled callbacks can receive unsanitized host objects. Supporting analysis also indicates the vulnerable implementation used Function.prototype.call in global Promise handler paths, which could be intercepted by attacker-controlled code; the fix replaced this with Reflect.apply. Successful exploitation allows code running inside the vm2 sandbox to break isolation, recover host-realm objects, reach the Function constructor, and execute arbitrary code in the underlying Node.js host environment.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation results in complete sandbox escape and arbitrary code execution on the underlying host running Node.js. An attacker able to execute untrusted JavaScript inside vm2 can access host-realm objects, pivot to the Function constructor, and run operating system commands via Node.js primitives such as child_process. This can lead to full compromise of the hosting process and, depending on deployment privileges, theft of secrets, modification of application state, lateral movement, and service disruption.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, do not treat vm2 as a sufficient security boundary for untrusted code. Avoid executing untrusted JavaScript in vm2 where feasible. Where use cannot be eliminated immediately, run the sandboxed workload inside a strongly isolated environment such as a dedicated container or VM with minimal privileges, no sensitive filesystem mounts or credentials, restricted network/egress, and host hardening controls such as seccomp, AppArmor, or SELinux. Apply defense in depth and assume sandbox escape is possible.

Remediation

Patch, then assume compromise.

Upgrade vm2 to version 3.10.2 or later, which fixes CVE-2026-22709. The provided content specifically identifies 3.10.2 as the version that addresses the Promise callback sanitization flaw, and some sources further recommend moving to the latest available vm2 release for additional fixes beyond this CVE. If vm2 remains deployed, review all applications and dependencies that invoke vm2 entry points for untrusted code execution and redeploy with the patched version.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
Vm2 ProjectVm2application

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity36

Community discussion across Reddit, Mastodon, and other social sources.