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

Sandbox escape via BaseHandler.getPrototypeOf in vm2

IdentifiersCVE-2026-44006CWE-94· Improper Control of Generation of…

CVE-2026-44006 is a critical vulnerability in the vm2 Node.js sandbox library. In affected versions prior to 3.11.0 (reported as affecting versions up to 3.10.5), attacker-controlled code running inside the vm2 sandbox can reach BaseHandler.getPrototypeOf. Access to this handler enables retrieval of arbitrary prototypes, which breaks vm2's proxy-based isolation model and allows traversal from sandboxed objects to host-side objects. The issue is described as a code injection vulnerability and a sandbox escape that can lead to arbitrary code execution on the host. Public reporting also associates the flaw with prototype traversal techniques used to escape the sandbox.

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 a sandboxed attacker to escape the vm2 isolation boundary and gain access to host-side object prototypes. In practice, this can enable arbitrary code execution in the host Node.js context, with resulting compromise of confidentiality, integrity, and availability. Depending on how vm2 is deployed, this may permit execution of operating system commands, access to sensitive application data, modification of application state, and full takeover of the process hosting the sandbox.

Mitigation

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

If immediate patching is not possible, avoid executing untrusted JavaScript in affected vm2 versions. Reduce exposure by disabling or suspending features that accept attacker-supplied code, isolating execution in separate hardened containers or microVMs, and applying strict OS-level sandboxing and least-privilege controls to the hosting process. Because this is a sandbox escape in the isolation boundary itself, compensating controls outside vm2 are more reliable than in-library restrictions.

Remediation

Patch, then assume compromise.

Upgrade vm2 to version 3.11.0 or later, as the vulnerability is fixed in 3.11.0. More recent reporting recommends upgrading to the latest available vm2 release for broader coverage of subsequently disclosed issues. If vm2 is used to execute untrusted code in high-risk or multi-tenant environments, reassess whether vm2 provides sufficient isolation for the threat model.
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 activity3

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