LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44005: vm2: Sandbox escape

vm2 is an open source vm/sandbox for Node.js. From 3.9.6 to 3.10.5, vm2's bridge exposes mutable proxies for real host-realm intrinsic prototypes and then forwards sandbox writes into the underlying host objects with otherReflectSet() and otherReflectDefineProperty(), which lets attacker-controlled JavaScript running in a default VM or inherited NodeVM mutate shared host Object.prototype, Array.prototype, and Function.prototype from inside the sandbox This vulnerability is fixed in 3.11.0.

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

Security readout for executives and security teams

Plain-English summary

vm2 is used to run JavaScript in a sandbox. In affected versions, code inside that sandbox can change shared host JavaScript prototypes, undermining the boundary and enabling integrity or availability impact. The advisory says 3.11.0 fixes the issue.

Executive priority

Treat this as urgent for any service that runs customer, tenant, or externally supplied JavaScript. Prioritize upgrade and exposure confirmation before routine dependency work because the issue affects sandbox isolation and can impact service integrity or availability.

Technical view

The vm2 bridge exposes mutable proxies for host-realm intrinsic prototypes and forwards sandbox writes into host objects. Attacker-controlled JavaScript in a default VM or inherited NodeVM can mutate host Object.prototype, Array.prototype, and Function.prototype. Affected versions are >=3.9.6 and <3.11.0.

Likely exposure

Exposure is likely in Node.js applications, automation platforms, developer tools, or SaaS features that use affected vm2 versions to execute untrusted or user-supplied JavaScript. The bundle identifies vm2 only; downstream product impact is not established here.

Exploitation context

The sources do not cite active exploitation, and the CVE is not marked KEV. The risk is still high because the vulnerability affects a sandbox boundary, requires no privileges or user interaction, and has a CVSS 3.1 score of 10.0.

Researcher notes

The provided evidence clearly establishes affected versions, root cause, impact class, CVSS, and fixed version. It does not establish public exploit availability, active exploitation, affected downstream products, or vendor-specific mitigations beyond upgrading vm2.

Mitigation direction

  • Upgrade vm2 to 3.11.0 or later where it is directly used.
  • Inventory transitive dependencies that include vm2 and update affected packages.
  • Pause untrusted JavaScript execution through affected vm2 paths until upgraded.
  • Check vendor and distribution advisories for packaged vm2 remediation status.
  • Retest sandbox-dependent features after upgrading vm2.

Validation and detection

  • Check lockfiles and SBOMs for vm2 versions >=3.9.6 and <3.11.0.
  • Identify code paths using default VM or inherited NodeVM with untrusted JavaScript.
  • Confirm deployed artifacts no longer contain affected vm2 versions.
  • Review container images and serverless bundles for stale dependency copies.
  • Monitor vendor advisories for downstream package status or revised guidance.
Prepared
Confidence
high
Sources
6

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-1321: 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-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 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
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-44005 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
10 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/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
5Source 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
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H3.95.8GitHub_M
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/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: Sandbox Escape leading to Arbitrary Code Execution
other:Red Hat severity ratingcvssV3_1
  • 2026-05-13T18:02:09.031Z: Reported to Red Hat.
  • 2026-05-13T17:40:41.578Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
patriksimekvm2>= 3.9.6, < 3.11.0Listed
Weakness

CWE details

CWE-1321CWE-653CWE-94

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