vm2 is a widely used Node.js sandbox library; this vulnerability allows sandbox escape and host RCE across many apps and services, posing broad, high-impact risk.
CVE-2026-92935
vm2 sandbox escape enabling RCE via array-shaped require
Is CVE-2026-92935 being exploited?
Not confirmed. CVE-2026-92935 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.
How severe is CVE-2026-92935?
CVE-2026-92935 is rated Critical with a CVSS score of 9.5. 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-92935?
Yes. A fix has been recorded for CVE-2026-92935. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-92935 affect?
CVE-2026-92935 affects vm2 v3.11.4 - v3.11.6, NodeVM in vm2-based Node.js applications, Host Node.js process running vm2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92935?
Upgrade to vm2 v3.11.7+; disable nesting or sanitize require; audit and rotate credentials if exposed
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape to arbitrary host RCE: attacker can spawn inner NodeVM with builtin allowlist (e.g., child_process) and execute commands as the host Node.js process.
Immediate action required
- affected>= 3.11.4 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.