LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24120: vm2: Sandbox Breakout Through Promise Species

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.10.5, the fix for CVE-2023-37466 is insufficient and can be circumvented allowing attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This issue has been patched in version 3.10.5.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

vm2 is meant to isolate untrusted Node.js code. Before 3.10.5, a prior sandbox-escape fix could be bypassed, allowing code inside the sandbox to break out and run commands on the host. This is a critical issue where exposure depends on whether an application lets attackers influence code executed through vm2.

Executive priority

Treat as urgent where vm2 processes untrusted code. A successful escape can turn a sandboxed script into host-level command execution, creating confidentiality, integrity, and availability risk.

Technical view

CVE-2026-24120 affects patriksimek/vm2 versions before 3.10.5. The advisory states the CVE-2023-37466 fix was insufficient and could be circumvented through Promise species behavior, enabling sandbox escape and arbitrary host command execution. CVSS 3.1 is 9.8 with network, low-complexity, unauthenticated, no-user-interaction characteristics.

Likely exposure

Node.js applications, services, plugins, CI systems, or internal tools using vm2 before 3.10.5 are potentially exposed, especially where vm2 runs user-controlled or third-party code.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation relevance depends on attacker access to code paths that execute supplied JavaScript inside vm2.

Researcher notes

Focus validation on reachability, not just package presence. Confirm whether attacker-controlled input can become code executed by vm2, then verify the exact loaded version at runtime and in packaged artifacts.

Mitigation direction

  • Upgrade vm2 to version 3.10.5 or later.
  • Check direct and transitive dependencies for vm2 before 3.10.5.
  • Rebuild and redeploy containers or bundles that include vulnerable vm2 versions.
  • Review GitHub, CVE, and Red Hat guidance for package-specific status.
  • If upgrade is blocked, seek vendor guidance before relying on compensating controls.

Validation and detection

  • Search package manifests and lockfiles for vm2 versions below 3.10.5.
  • Check SBOMs and dependency scanner output for vulnerable vm2 instances.
  • Confirm deployed artifacts no longer include vm2 before 3.10.5.
  • Review Red Hat CVE and VEX records for environment-specific applicability.
  • Identify whether any service executes untrusted JavaScript through vm2.
Prepared
Confidence
high
Sources
7

Public sources used

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-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 lookup
cwe · low confidence lookup

CWE-807: 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 lookup
cwe · medium confidence lookup

CWE-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 lookup
cve · low confidence lookup

CVE-2026-24120 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_M
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-24120Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPvm2: vm2: Arbitrary code execution due to sandbox escape vulnerability
other:Red Hat severity ratingcvssV3_1
  • 2026-05-04T19:03:34.685Z: Reported to Red Hat.
  • 2026-05-04T16:31:13.639Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
patriksimekvm2< 3.10.5Listed
Weakness

CWE details

CWE-693CWE-807CWE-94

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.