Skip to content
major vulnerability· requires attention

Sandbox escape RCE in vm2 (CVSS 10) affects many Node.js apps and platforms that embed vm2; widespread impact on systems running untrusted code.

Applications

CVE-2026-92937

10.0
Critical
EPSS n/aPatch availableSep 19, 2026

vm2 sandbox escape allowing host Node.js remote code execution via crafted Promise.call/apply

common questions

Is CVE-2026-92937 being exploited?

Not confirmed. CVE-2026-92937 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-92937?

CVE-2026-92937 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-92937?

Yes. A fix has been recorded for CVE-2026-92937. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-92937 affect?

CVE-2026-92937 affects vm2 3.11.6, Node.js applications embedding vm2, services exposing host Promises to sandboxes, npm packages using vm2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-92937?

Upgrade vm2 to 3.11.7 immediately and audit exposed host Promises

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
vm2 3.11.6Node.js applications embedding vm2services exposing host Promises to sandboxesnpm packages using vm2
impact

Sandbox escape yields full RCE in host Node.js process; attacker can run arbitrary commands and access host objects (e.g., spawn child_process).

action required

Immediate action required

affected versions
patriksimek vm2
  • affected>= 3.11.6 and < 3.11.7
vendor says fixed in3.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free