vm2 is a widely used Node.js sandbox; this bug allows sandboxed code to escape and hijack host DNS/global state, posing high supply-chain and runtime risk that will be widely reported.
CVE-2026-92960
vm2 sandbox flaw allows process-wide DNS/OS exposure and sandbox escape.
do firstUpgrade to a fixed release: 3.11.6.
Is CVE-2026-92960 being exploited?
Not confirmed. CVE-2026-92960 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-92960?
CVE-2026-92960 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-92960?
Yes. A fix has been recorded for CVE-2026-92960. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-92960 affect?
CVE-2026-92960 affects vm2 < 3.11.6, Node.js applications using vm2, Services executing untrusted JavaScript. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92960?
Upgrade vm2 to >=3.11.6, remove builtin:['*'] and audit/all runtimes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape: read host identity/network topology and call dns.setServers() to hijack host DNS resolver, enabling traffic redirection and monitoring.
Immediate action required
- affected< 3.11.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- poc
- automatable
- yes
- technical impact
- total
Assessed by CISA 17 Sept 2026 (SSVC 2.0.3).
timeline
- 17 Sept 2026Published
- 17 Sept 2026CISA SSVC assessment: exploitation poc · same day later
- 17 Sept 2026CVE record last updated · same day later
- 19 Sept 2026Analysed by vulneraibility.com · 2 days later
also known as
- Advisorygithub.com /patriksimek/vm2/security/advisories/GHSA-m5w8-4gq2-6f8x
- Advisoryvulncheck.com /advisories/vm2-before-3.11.6-process-wide-state-exposure-via-os-and-dns
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.