Security readout for executives and security teams
Plain-English summary
Applications using vulnerable vm2 configurations may let untrusted sandboxed JavaScript escape its restrictions and run code on the host. Successful exploitation could expose data, alter systems, or disrupt services. The flaw affects vm2 versions before 3.11.0 when NodeVM permits the module builtin directly or through the '*' wildcard.
Executive priority
Treat confirmed exposed deployments as an urgent remediation item. Upgrade internet-facing or multi-tenant code-execution services first, then internal systems processing untrusted content. Where exposure prerequisites are absent, document that finding rather than assigning equal urgency. No active exploitation is established by the supplied sources.
Technical view
NodeVM's builtin allowlist is bypassed because the permitted module builtin exposes Node.js Module._load(). That loader resolves modules in the host context, allowing sandboxed code to access otherwise excluded builtins such as child_process. This breaks the sandbox boundary and can result in remote code execution with the hosting process's privileges.
Likely exposure
Exposure requires vm2 earlier than 3.11.0, use of NodeVM, permission for the module builtin explicitly or through '*', and execution of attacker-influenced JavaScript. Internet-facing services that evaluate user-supplied code have the greatest business risk. Deployments not meeting these conditions are not shown affected by the supplied evidence.
Exploitation context
The supplied record assigns CVSS 9.9 because exploitation is low-complexity, requires limited privileges, needs no user interaction, and crosses a security boundary. The bundle marks KEV false and provides no evidence of active exploitation. That absence does not prove exploitation has never occurred.
Researcher notes
The security boundary failure occurs through a host-context loader, not merely an incomplete list of allowed builtins. Assessment should therefore examine both resolved package versions and runtime NodeVM options. The record associates CWE-829 and CWE-863. The supplied material does not identify public exploitation, observed indicators, or affected downstream products beyond vm2 and referenced Red Hat packaging.
Mitigation direction
- Upgrade vm2 to version 3.11.0 or later.
- Prioritize systems that execute untrusted or externally supplied JavaScript.
- Until upgraded, remove permission for the module builtin and avoid the '*' builtin wildcard.
- Restrict affected application processes using least privilege and host-level isolation.
- Follow applicable vendor guidance, including Red Hat advisories for packaged deployments.
Validation and detection
- Inventory direct and transitive vm2 installations and record their resolved versions.
- Confirm affected workloads use NodeVM rather than assuming every vm2 installation is exploitable.
- Review NodeVM builtin configuration for module or '*' permissions.
- Verify production deployments resolve vm2 version 3.11.0 or later.
- Safely confirm sandboxed code cannot access excluded builtins after remediation.
- Review telemetry for unexpected subprocess creation or commands originating from sandbox-hosting services.
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-829: 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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-43999 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
2 official scoresWe 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_MCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16redhat-SADPVulnerability 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
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.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-13T18:01:40.919Z: Reported to Red Hat.
- 2026-05-13T17:21:22.308Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-947f-4v7f-x2v8CVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-43999CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2477196CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43999.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:50850CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
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.