LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44007: vm2: nesting: true bypasses require: false, allowing sandbox escape to arbitrary OS command execution

vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.1, when a NodeVM is created with nesting: true, sandbox code can unconditionally require('vm2') regardless of the outer VM's require configuration — including require: false. With access to vm2, the sandbox constructs a new inner NodeVM with its own unrestricted require settings and executes arbitrary OS commands on the host. Any application that runs untrusted code inside a NodeVM with nesting: true is fully compromised. This vulnerability is fixed in 3.11.1.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Applications using affected vm2 configurations to run untrusted JavaScript may allow that code to escape its intended sandbox and execute operating-system commands. A successful compromise could expose or alter host data and disrupt services. The flaw is fixed in vm2 3.11.1.

Executive priority

Treat confirmed affected deployments as an immediate remediation priority because successful exploitation grants host-level command execution with confidentiality, integrity, and availability impact. Prioritize services accepting customer, tenant, plugin, or other untrusted code.

Technical view

Before vm2 3.11.1, NodeVM with nesting enabled permits sandboxed code to load vm2 even when require is disabled. It can then create an inner NodeVM with unrestricted module access, escaping the outer security policy and reaching host command execution. The CVSS 3.1 score is 9.9.

Likely exposure

Exposure requires vm2 earlier than 3.11.1, NodeVM, nesting set to true, and execution of untrusted code. Applications without this configuration are not identified as affected by the supplied evidence. Internet exposure depends on whether external users can submit code to the application.

Exploitation context

The supplied bundle does not establish active exploitation, and this CVE is not listed as KEV in the bundle. Exploitation nevertheless has low stated complexity and requires access sufficient to supply code to the vulnerable sandbox; no user interaction is required.

Researcher notes

The issue is categorized under CWE-1100 and CWE-284. The security boundary fails because the nested VM can redefine module-access policy. Scope changed in the CVSS vector, supporting impact beyond the sandbox. The supplied evidence names no specific detection signature or confirmed exploitation campaign.

Mitigation direction

  • Upgrade vm2 to version 3.11.1 or later.
  • Disable NodeVM nesting until the upgrade is complete.
  • Suspend untrusted-code execution where neither upgrade nor configuration change is immediately possible.
  • Review vendor and distribution advisories for environment-specific packages and updates.

Validation and detection

  • Inventory direct and transitive vm2 versions in applications and deployed artifacts.
  • Identify every NodeVM configuration and verify whether nesting is enabled.
  • Confirm externally supplied or otherwise untrusted code cannot reach affected configurations.
  • Verify production deployments resolve vm2 to version 3.11.1 or later.
  • Review relevant execution records for suspicious activity; the supplied sources provide no specific indicators.
Prepared
Confidence
high
Sources
5

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-1100: 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-284: 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 lookup
description · low confidence lookup

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

CVE-2026-44007 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.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

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
3ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical 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.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16redhat-SADP
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPvm2: vm2: Arbitrary code execution via nested NodeVM bypass
other:Red Hat severity ratingcvssV3_1
  • 2026-05-13T18:01:46.215Z: Reported to Red Hat.
  • 2026-05-13T17:33:19.799Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
patriksimekvm2< 3.11.1Listed
Weakness

CWE details

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

CWE-1100 · source CWE mapping

Insufficient Isolation of System-Dependent Functions

Insufficient Isolation of System-Dependent Functions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.