CVE-2026-44008: vm2: Snabox breakout via `neutralizeArraySpeciesBatch`
vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.2, the new method neutralizeArraySpeciesBatch works with objects from the other side but can call into this side via getter on the array prototype exposing objects of the wrong side into the sandbox. This can be used to get host objects and get the host Function object. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This vulnerability is fixed in 3.11.2.
Security readout for executives and security teams
Plain-English summary
Applications using vm2 to isolate untrusted Node.js code may not actually contain it. An attacker reaching that functionality could escape the sandbox and run commands on the host, potentially compromising data, software, and service availability. The source bundle rates this critical and identifies vm2 versions before 3.11.2 as affected.
Executive priority
Treat this as an urgent remediation for internet-facing or multi-tenant services that use vulnerable vm2 versions. Sandbox escape can turn limited code execution into host compromise. Establish exposure immediately, upgrade affected deployments, and investigate suspicious host activity. Systems without vm2 or already running 3.11.2 or later are outside the stated affected range.
Technical view
A cross-boundary flaw in neutralizeArraySpeciesBatch permits a getter on the array prototype to expose host-side objects inside the sandbox. Attackers may obtain the host Function object, escape vm2, and execute arbitrary host commands. The supplied CVSS 3.1 score is 9.8. Version 3.11.2 contains the fix.
Likely exposure
Exposure exists where vm2 versions earlier than 3.11.2 execute attacker-controlled or otherwise untrusted code. Practical reachability depends on how the application invokes vm2 and whether external users can submit code or influence sandboxed execution. The bundle does not identify specific downstream applications or deployments.
Exploitation context
The issue requires attacker-controlled input to reach a vulnerable vm2 sandbox. The supplied vector reports network reachability, low complexity, no privileges, and no user interaction, but application architecture determines actual access. The bundle marks KEV false and provides no evidence of active exploitation or a public proof of concept.
Researcher notes
The core trust-boundary failure involves cross-realm object handling through an array-prototype getter during neutralizeArraySpeciesBatch. CWE-1100 and CWE-668 are listed. Confirm exploitability in a controlled environment without using production payloads. The bundle establishes arbitrary host command execution potential but does not document observed exploitation, affected downstream products, or environmental preconditions beyond vulnerable vm2 use.
Mitigation direction
Upgrade vm2 to version 3.11.2 or later.
Prioritize systems that run externally supplied or untrusted code.
Restrict access to sandbox-backed functionality until remediation is verified.
Review the vm2 advisory and relevant vendor guidance for deployment-specific instructions.
Validation and detection
Inventory direct and transitive vm2 versions in deployed applications.
Confirm resolved dependency trees contain vm2 3.11.2 or later.
Identify routes, jobs, or services that pass untrusted input into vm2.
Run existing application security and regression tests after upgrading.
Review host logs for unexpected child processes or commands from sandbox services.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1100: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1100 · source CWE mapping
Insufficient Isolation of System-Dependent Functions
Insufficient Isolation of System-Dependent Functions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.