vm2 NodeVM Remote Code Execution via Array-Shaped Require (CVE-2026-92935)
Published Last modified Sources: Red Hat, OSV, CVE.org, Hersteller, BSI
What is affected, what to do
A flaw was found in vm2. This vulnerability allows an attacker who can execute untrusted JavaScript inside the sandbox to achieve arbitrary code execution on the host system.
An exploit is publicly available. Update Patriksimek Vm2 to version 3.11.7.
- Affected
- Patriksimek Vm2
lt 3.11.4..3.11.7
- Patriksimek Vm2
- Fixed in
- Patriksimek Vm2
3.11.7
- Patriksimek Vm2
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v4
9.0
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: Red Hat, OSV, CVE.org, Hersteller, BSI
0.7 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 52.0
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 96.85 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- PoC (publicly reported)
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.0
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.7 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 52.0
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-913
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in vm2. This vulnerability allows an attacker who can execute untrusted JavaScript inside the sandbox to achieve arbitrary code execution on the host system. By providing an array value to the require configuration when nested sandboxes are enabled, the attacker can bypass isolation boundaries. Consequently, the attacker can escape sandbox containment and execute unauthorized commands with the privileges of the underlying Node.js process.
Source: redhat_csaf, OSV (Open Source Vulnerabilities), NVD (NIST), cvelistv5, GitHub Security Advisories, BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| patriksimek | vm2 |
|
|
| Open Source | vm2 |
|
|
| npm | vm2 |
|
|
Vendors and products
Weakness classes (CWE)
CWE-913Improper Control of Dynamically-Managed Code Resources
Class
The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.
Entry at MITRE CWE-913
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CIRCL Sightings | GitHub Security Advisories (opens in a new tab) | PoC (publicly reported)reported, not verified |
References & sources
- github.comGitHub Security Advisory (GHSA-8hr7-r645-pc6w)Vendor advisory
- github.comPatch CommitPatch
- vulncheck.comVulnCheck Advisory: vm2 NodeVM Remote Code Execution via Array-Shaped RequireThird-party advisory
- NVD (NIST)vuln/detail/CVE-2026-92935advisory
- github.compatriksimek/vm2/commit/05894eca1dc6a2b1a986f312c88255288a983d22web
- github.compatriksimek/vm2package
- github.compatriksimek/vm2/releases/tag/v3.11.7web
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-92935","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-17T18:57:25.525605Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedVulnCheck
CVSS V4.0: AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CVSS V3.1: AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Weakness type: CWE-913
Description added or changed
Show 8 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —vm2 is a sandbox for running untrusted Node.js code. In versions >= 3.11.4 and <= 3.11.6, the NodeVM constructor computes `hasRealRequireConfig` with `typeof requireOpts === 'object' && requireOpts !== null`, so an array-shaped `require` value (for example `require: []`) satisfies the guard that is meant to reject nesting without an explicit require configuration. `makeResolverFromLegacyOptions()` then destructures the array into undefined option fields and returns a resolver containing only `NESTING_OVERRIDE.vm2`. As a result, an attacker who can supply JavaScript executed by a NodeVM configured with truthy `nesting` and an array-shaped `require` (e.g. `new NodeVM({nesting: true, require: []})`) can require the host `vm2` module, create an inner NodeVM with an attacker-chosen builtin allowlist (such as `child_process`), and execute arbitrary commands with the privileges of the host Node.js process, escaping the sandbox. Outer builtin restrictions do not constrain the attacker-created inner NodeVM. This issue is fixed in vm2 3.11.7.CVSS added —AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS added —AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HWeakness type (CWE) added —CWE-913Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/92xxx/CVE-2026-92935.json">CVE-2026-92935</a>Reference added —https://github.com/patriksimek/vm2/commit/54b54b74a382577f0bcd0538c5bf99acdcd7f53bReference added —https://github.com/patriksimek/vm2/security/advisories/GHSA-8hr7-r645-pc6wReference added —https://www.vulncheck.com/advisories/vm2-nodevm-remote-code-execution-via-array-shaped-requireSource identifier: disclosure@vulncheck.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-92935"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-92935.svg?lang=en" alt="CVE-2026-92935 – NEOSEC Intel" height="20"></a>