Critical sandbox escape in the widely-used vm2 Node.js library enabling host RCE across many deployments; urgent org-wide attention required.
CVE-2026-92956
vm2 sandbox escape on Node.js 26 via WebAssembly → host RCE
do firstUpgrade to a fixed release: 3.11.7.
Is CVE-2026-92956 being exploited?
Not confirmed. CVE-2026-92956 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.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-92956?
CVE-2026-92956 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-92956?
Yes. A fix has been recorded for CVE-2026-92956. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-92956 affect?
CVE-2026-92956 affects vm2 3.10.1 - 3.11.6, Node.js 26 runtime, Applications embedding vm2 sandboxes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92956?
Upgrade vm2 to 3.11.7 immediately; isolate and audit sandboxed hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandboxed code can recover host process and execute arbitrary Node.js code (RCE, access to fs/modules).
Immediate action required
- affected>= 3.10.1 and < 3.11.7
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.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- none
- 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 none · same day later
- 17 Sept 2026CVE record last updated · same day later
- 19 Sept 2026Analysed by vulneraibility.com · 1 day later
- 12 Oct 2026First proof-of-concept repository on GitHub (unvetted) · 23 days later
also known as
- Advisorygithub.com /patriksimek/vm2/security/advisories/GHSA-wjwh-qqvp-g4p4
- Advisoryvulncheck.com /advisories/vm2-3.10.1-through-3.11.6-sandbox-escape-via-webassembly-compilestre
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
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- 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.