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

vm2 Promise Species Sandbox Escape

IdentifiersCVE-2026-47208CWE-913· Improper Control of…

CVE-2026-47208 is a sandbox breakout vulnerability in vm2, the Node.js sandbox library, affecting versions prior to 3.11.4. According to the provided content, the flaw is caused by vm2 failing to clear promise constructor species definitions after changes to localPromise handling. By supplying a custom Promise with a fabricated rejection path, an attacker can cause vm2 to expose a raw host-originated error object to attacker-controlled code. Access to that host object can then be leveraged to escape the sandbox boundary and execute arbitrary commands on the host system.

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 allows code running inside a vm2 sandbox to break out of the sandbox and achieve arbitrary command execution on the underlying host. The provided content indicates high impact to confidentiality, integrity, and availability, consistent with full compromise of the host process context and access to host-side resources such as files, secrets, credentials, tokens, processes, and application data.

Mitigation

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

The available information indicates there are no effective configuration-based workarounds when untrusted scripts are permitted to run inside vm2. Until patched, the practical mitigation is to stop executing untrusted code in affected vm2 instances, isolate the workload at a stronger boundary, and upgrade to 3.11.4 or later as soon as possible.

Remediation

Patch, then assume compromise.

Upgrade vm2 to version 3.11.4 or later. The provided content states that the issue is patched in vm2 3.11.4.
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.

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 activity4

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