Security readout for executives and security teams
Plain-English summary
Applications using vm2 to run untrusted JavaScript may not be safely isolated. An attacker able to submit code to the sandbox could reach the host environment, potentially compromising sensitive data, application integrity, and service availability. vm2 versions before 3.11.0 are affected.
Executive priority
Treat this as an immediate remediation priority for any reachable untrusted-code execution service. Rapidly identify affected deployments, upgrade them, and constrain host privileges. Systems containing vm2 but lacking an untrusted input path remain affected by version, although their practical exposure may be lower.
Technical view
CVE-2026-43997 is a vm2 sandbox escape caused by access to the host Object. The advisory identifies host-object property-symbol handling as one route across the isolation boundary. The CVSS 3.1 score is 10.0, reflecting remotely reachable, low-complexity compromise without privileges or user interaction when an exposed application accepts untrusted code.
Likely exposure
Exposure is highest where vm2 versions below 3.11.0 execute user-controlled or externally supplied JavaScript. Dependency presence alone does not prove reachability; teams must determine whether untrusted input can enter a vm2 sandbox and what host permissions the Node.js process holds.
Exploitation context
The supplied sources describe a practical sandbox-escape condition, but do not establish active exploitation in the wild. The CVE is not identified as a CISA KEV entry in the supplied bundle. Treat reachable deployments as urgent because successful exploitation could cross the intended trust boundary with broad impact.
Researcher notes
The assigned weaknesses include CWE-653 and CWE-94. The central security failure is loss of separation between sandboxed JavaScript and host objects. Researchers should assess application-specific reachability and host-process privilege without testing production destructively. The supplied evidence confirms the affected range and fixed release, but not observed exploitation or every possible escape path.
Mitigation direction
- Upgrade vm2 to version 3.11.0 or later.
- Prioritize internet-facing services that execute untrusted JavaScript.
- Disable untrusted-code execution until upgrading if immediate remediation is impossible.
- Reduce the Node.js process permissions and access to secrets.
- Review applicable Red Hat guidance for packaged dependencies.
Validation and detection
- Inventory direct and transitive vm2 installations and record resolved versions.
- Confirm no deployed instance resolves to a version below 3.11.0.
- Trace whether external input can reach vm2 code-execution paths.
- Verify upgraded services start correctly and retain required sandbox behavior.
- Review logs for suspicious activity around sandbox execution interfaces.
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-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.
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 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-43997 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
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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:N/UI:N/S:C/C:H/I:H/A:H3.96GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/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:02:02.030Z: Reported to Red Hat.
- 2026-05-13T17:17:54.869Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-47x8-96vw-5wg6CVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-43997CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2477203CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43997.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.
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.
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.