Security readout for executives and security teams
Plain-English summary
Applications using vm2 before 3.11.6 may fail to contain untrusted JavaScript. Under the documented conditions, sandboxed code can reach a powerful host object and run commands with the Node.js application's privileges, threatening sensitive data, application integrity, and service availability.
Executive priority
Treat as an urgent remediation for any production service executing untrusted code with vm2. Patch immediately where the documented conditions exist; rapidly inventory other systems. Business risk includes application takeover under the service account's permissions, although active exploitation is not established by the supplied evidence.
Technical view
The sandbox exception handler sanitizes several nested error properties but omits Error.cause. If an embedder-exposed host function throws an error whose cause contains a powerful host object such as process, sandboxed code may recover that object, escape isolation, and achieve host command execution. Version 3.11.6 fixes the issue.
Likely exposure
Exposure requires vm2 below 3.11.6 and the ability to execute attacker-controlled sandbox code. The documented escape also depends on an exposed host function returning a powerful object through Error.cause. Internet exposure increases concern but is not stated as mandatory.
Exploitation context
The supplied record marks this CVE as absent from KEV, and no provided source establishes active exploitation. Exploitation is conditional rather than automatic, but the low-complexity sandbox escape can have complete confidentiality, integrity, and availability impact when those conditions exist.
Researcher notes
CVSS 3.1 is 9.9 with network reachability, low complexity, low privileges, no interaction, changed scope, and high impact. Assess exploitability per integration: vulnerable version alone is insufficient; confirm attacker-controlled sandbox execution and a host-function error path capable of exposing a powerful object through Error.cause.
Mitigation direction
- Upgrade vm2 to version 3.11.6 or later.
- Temporarily prevent untrusted code from executing in affected vm2 sandboxes.
- Review embedder-exposed host functions and avoid placing powerful host objects in thrown error causes.
- Prioritize systems where sandboxed code is supplied by customers, plugins, or other untrusted sources.
Validation and detection
- Inventory direct and transitive vm2 dependencies across source, lockfiles, images, and deployed applications.
- Confirm each deployed runtime resolves vm2 version 3.11.6 or later.
- Identify whether untrusted users or integrations can submit code to vm2.
- Review exposed host functions for errors carrying sensitive objects through Error.cause.
- Run safe regression tests confirming host objects cannot cross the sandbox through Error.cause.
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 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-47686 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.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
SSVC decision data
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:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-m283-3h24-438vCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/patriksimek/vm2/commit/7e3faaf550f4ab975bf4cdde183fcec49b056d8eCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/patriksimek/vm2/releases/tag/3.11.6CVE reference, GitHub_M · 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.