CVE-2026-24781: vm2: Sandbox Breakout Through Inspect
vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.0, VM2 suffers from a sandbox breakout vulnerability through the inspect function. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This issue has been patched in version 3.11.0.
Security readout for executives and security teams
Plain-English summary
CVE-2026-24781 is a critical vm2 sandbox escape. Applications that rely on vm2 to safely run untrusted Node.js code may allow that code to break out and run commands on the host. The vendor states the issue affects versions before 3.11.0 and is patched in 3.11.0.
Executive priority
Treat as urgent for any system running untrusted code with vm2. Prioritize internet-facing, multi-tenant, automation, CI, and developer-sandbox services first because compromise can reach the host system.
Technical view
vm2 before 3.11.0 has a sandbox breakout through the inspect function. The CVE reports arbitrary host command execution with CVSS 9.8, network attack vector, low complexity, no privileges, and no user interaction. CWE mappings include improper isolation, protection mechanism failure, and code injection.
Likely exposure
Most likely exposure is Node.js services, developer platforms, workflow systems, or internal tooling that execute untrusted or user-controlled JavaScript through vm2 versions below 3.11.0.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. Practical risk depends on whether attackers can influence code executed inside vm2. If they can, the reported impact is full host compromise.
Researcher notes
Evidence supports affected range and fixed version, but the prompt bundle does not include exploit maturity details. Avoid assuming downstream Red Hat product exposure without reviewing the cited Red Hat advisories and VEX data.
Mitigation direction
Upgrade vm2 to version 3.11.0 or later.
Inventory direct and transitive vm2 dependencies.
Review Red Hat advisories if using affected Red Hat products.
Restrict untrusted code execution until remediation is complete.
Check vendor guidance for any environment-specific mitigations.
Validation and detection
Search dependency manifests and lockfiles for vm2.
Confirm deployed runtime versions are not below 3.11.0.
Identify features that execute user-controlled JavaScript in vm2.
Review SBOMs and container images for bundled vm2 copies.
Track vendor advisories for downstream package status.
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-653: 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.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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
11Source 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-653 · source CWE mapping
Improper Isolation or Compartmentalization
Improper Isolation or Compartmentalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.