Security readout for executives and security teams
Plain-English summary
CVE-2026-22709 lets untrusted JavaScript break out of the vm2 sandbox in Node.js. If your application uses vm2 to run customer, tenant, plugin, or AI-generated code, compromise could become full code execution in the application environment. The disclosed fix is vm2 3.10.2.
Executive priority
High priority for any product using vm2 as a security boundary. A successful escape could undermine isolation and lead to application takeover. Patch promptly, starting with externally exposed, multi-tenant, or customer-code execution environments.
Technical view
In vm2 before 3.10.2, Promise callback sanitization can be bypassed. The advisory says localPromise.prototype.then callbacks are sanitized, but globalPromise.prototype.then is not; async functions return globalPromise objects. This can allow sandbox escape and arbitrary code execution. CVSS is 9.8 critical.
Likely exposure
Exposure is likely where Node.js applications include vm2 versions earlier than 3.10.2 and use it to execute untrusted or semi-trusted JavaScript. Risk is lower if vm2 is present but not reachable with attacker-controlled code.
Exploitation context
The public sources describe a sandbox escape with network-adjacent characteristics under CVSS, but they do not state active exploitation. The CVE is not marked KEV in the provided bundle. Treat internet-facing or multi-tenant sandbox use as urgent.
Researcher notes
Focus validation on dependency version and whether async Promise paths are reachable from untrusted sandboxed code. Do not assume presence equals exploitability; confirm vm2 is used as a runtime boundary. Sources only identify 3.10.2 as the fix.
Mitigation direction
- Upgrade vm2 to version 3.10.2 or later where it is used.
- Prioritize systems running untrusted, tenant-supplied, plugin, or generated JavaScript.
- If immediate upgrade is not possible, check vendor guidance for supported compensating controls.
- Limit sandboxed code execution to trusted sources until remediation is complete.
Validation and detection
- Inventory Node.js projects for vm2 dependencies and transitive dependencies.
- Confirm deployed vm2 versions are 3.10.2 or later.
- Map whether vm2 executes attacker-controlled or tenant-controlled JavaScript.
- Review CI and production artifacts, not only source manifests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-693: 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.
Open ATT&CK lookupCWE-913: 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.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
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.
Open ATT&CK lookupExecution behavior lookup
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.
Open ATT&CK lookupPrivilege behavior lookup
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.
Open ATT&CK lookupCVE-2026-22709 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-99p7-6v5w-7xg8CVE reference · x_refsource_CONFIRM
- https://github.com/patriksimek/vm2/commit/4b009c2d4b1131c01810c1205e641d614c322a29CVE reference · x_refsource_MISC
- https://github.com/patriksimek/vm2/releases/tag/v3.10.2CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Dynamically-Managed Code Resources
Improper Control of Dynamically-Managed Code Resources 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.