vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, a sandbox escape vulnerability in vm2 v3.10.5 allows any sandboxed code to crash the host Node.js process via a single Promise constructor that triggers an unhandled rejection propagating to the host. The fix for CVE-2026-22709 (v3.10.2) only sanitized the onRejected callback in .then() and .catch() overrides and did not address the executor-to-unhandledRejection path. This vulnerability is fixed in 3.11.0.
Security readout for executives and security teams
Plain-English summary
CVE-2026-44001 affects vm2, a Node.js sandbox library. In versions before 3.11.0, code running inside the sandbox can escape intended error handling enough to crash the host Node.js process. The documented impact is denial of service, not data theft or code execution.
Executive priority
Treat this as a high-priority availability issue for any service that runs untrusted JavaScript through vm2. Patch quickly where vm2 is internet-facing or multi-tenant; otherwise prioritize through normal dependency remediation.
Technical view
The issue is an unhandled rejection path involving a Promise constructor. Prior fixes for CVE-2026-22709 covered .then() and .catch() onRejected handling but did not sanitize the executor-to-unhandledRejection path. CVSS 8.6 reflects network attackability, low complexity, no privileges, changed scope, and high availability impact.
Likely exposure
Exposure is likely where applications use vm2 before 3.11.0 to run untrusted or user-supplied JavaScript. Risk is higher when sandboxed execution is reachable through public APIs, automation, plugin systems, or multi-tenant services.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. The advisory describes a simple crash condition from sandboxed code, but provides no evidence of confidentiality or integrity impact.
Researcher notes
The evidence supports a sandbox-isolation flaw causing host process denial of service through Promise rejection handling. Sources do not support claims of arbitrary code execution, data access, or active exploitation. Prior CVE-2026-22709 remediation was incomplete for this path.
Mitigation direction
Upgrade vm2 to 3.11.0 or later.
Inventory direct and transitive vm2 dependencies.
Temporarily restrict untrusted JavaScript execution until upgraded.
Check vendor advisory and Red Hat tracking for updated guidance.
Use process supervision to reduce outage duration after crashes.
Validation and detection
Check package manifests, lockfiles, and SBOMs for vm2 versions below 3.11.0.
Confirm deployed services load the upgraded vm2 package.
Identify public or tenant-facing features that execute sandboxed JavaScript.
Review crash logs for Node.js unhandled rejection process exits.
Confirm dependency scanners flag and close CVE-2026-44001.
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-248: 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.
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.
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-248 · source CWE mapping
Uncaught Exception
Uncaught Exception represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.