vm2 is an open source vm/sandbox for Node.js. In version 3.10.4, vm2 is vulnerable to full sandbox escape with arbitrary code execution. Attacker code inside VM.run() obtains host process object and runs host commands with zero host cooperation. This issue has been patched in version 3.10.5.
Security readout for executives and security teams
Plain-English summary
CVE-2026-26956 is a critical sandbox escape in vm2 3.10.4, limited by the source bundle to Node.js 25. Code intended to be confined inside vm2 can break out and execute with the host process's authority. Any service using vm2 to run untrusted JavaScript should treat this as urgent.
Executive priority
Treat as an emergency fix for systems that run untrusted code with vm2 on Node.js 25. The business risk is host compromise from a component specifically intended to isolate code. Patch quickly, validate deployment, and confirm whether any externally reachable workflow can trigger vm2 execution.
Technical view
The advisory describes full sandbox escape and arbitrary code execution from attacker-controlled code passed to VM.run(). The affected package is patriksimek/vm2 version 3.10.4, with a fix in 3.10.5. CVSS is 9.8: network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in applications or platforms that run untrusted JavaScript through vm2 3.10.4 on Node.js 25. Risk is lower where vm2 is absent, upgraded, unused for untrusted code, or not running on Node.js 25. Red Hat product exposure should be checked against its linked CVE and VEX records.
Exploitation context
The bundle states attacker code inside VM.run() can obtain the host process object and run host commands without host cooperation. KEV is false, and the provided sources do not establish active exploitation in the wild. Public exploit availability is not confirmed by the supplied evidence.
Researcher notes
Core facts are source-grounded: affected version 3.10.4, patch 3.10.5, Node 25 scope, CVSS 9.8, CWE-653 and CWE-693. The sources do not provide exploit telemetry, proof of KEV listing, or detailed downstream affected-product mapping. Avoid assuming older vm2 lines or non-Node-25 runtimes are affected from this bundle alone.
Mitigation direction
Upgrade vm2 from 3.10.4 to 3.10.5 or later where available.
Prioritize services executing untrusted JavaScript through VM.run().
Confirm deployed artifacts use the patched dependency, not only source manifests.
Review vendor guidance for downstream packages and Red Hat applicability.
Reduce or suspend untrusted-code execution until patched if immediate upgrade is blocked.
Validation and detection
Search dependency manifests, lockfiles, SBOMs, and containers for vm2 3.10.4.
Confirm affected services are running, or could run, on Node.js 25.
Identify code paths that pass untrusted input into VM.run().
Verify production images and runtime bundles contain vm2 3.10.5 or later.
Check vendor advisories for distribution-specific status and backports.
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.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-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.