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
CVE-2026-44008 is a critical vm2 sandbox escape. Applications that rely on vm2 before 3.11.2 to safely run untrusted JavaScript may allow that code to break out and execute commands on the host system.
Executive priority
Prioritize remediation immediately for any system running untrusted JavaScript through vm2. The business risk is full compromise of the host running the sandbox, not just application-level data exposure.
Technical view
In vm2 before 3.11.2, neutralizeArraySpeciesBatch can interact with cross-side objects and trigger a getter on the array prototype. That can expose host-side objects inside the sandbox, leading to access to the host Function object and arbitrary command execution.
Likely exposure
Exposure is likely where Node.js applications include vm2 versions below 3.11.2 and use it for untrusted or semi-trusted JavaScript execution, such as plugin, automation, or user-code features. Node.js alone is not enough; vm2 usage is the key condition.
Exploitation context
The source bundle states the issue can allow VM2 sandbox escape and host command execution. It does not provide evidence of active exploitation, and KEV status is false. Treat internet-facing or tenant-facing sandbox use as urgent because attack complexity and privileges are rated low/none.
Researcher notes
Focus triage on dependency version and whether vm2 handles attacker-controlled code. The advisory attributes the flaw to cross-context object handling through neutralizeArraySpeciesBatch and array prototype getter behavior. Do not assume exploitation without external evidence.
Mitigation direction
Upgrade vm2 to version 3.11.2 or later.
Rebuild and redeploy lockfiles and containers after upgrading.
Temporarily disable vm2-backed untrusted code execution if patching is delayed.
Check vendor and Red Hat guidance for environment-specific status.
Reduce host privileges for sandbox worker processes where feasible.
Validation and detection
Search package manifests and lockfiles for vm2 below 3.11.2.
Confirm production artifacts contain vm2 3.11.2 or later.
Map features that execute user, plugin, or tenant-supplied JavaScript.
Verify exposed sandbox services were rebuilt after dependency updates.
Review SBOM and container scan results for stale vm2 copies.
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
5Source 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.