Skip to content
major vulnerability· requires attention

High-impact remote sandbox escape in a widely used Node.js sandbox library (vm2) enabling host RCE; affects many Node apps and services that embed vm2.

Applications

CVE-2026-93606

10.0
Critical
EPSS 0.52%Patch availableSep 20, 2026

vm2 Promise-based sandbox escape allows host remote code execution

common questions

Is CVE-2026-93606 being exploited?

Not confirmed. CVE-2026-93606 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.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-93606?

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

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

What does CVE-2026-93606 affect?

CVE-2026-93606 affects vm2 (npm) <= 3.12.0, Node.js applications embedding vm2, Services using vm2 for sandboxing/untrusted code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-93606?

Upgrade vm2 to >=3.12.1, audit/disable sandboxes and block untrusted code execution.

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

executive summary
technical analysis
affected
vm2 (npm) <= 3.12.0Node.js applications embedding vm2Services using vm2 for sandboxing/untrusted code
impact

Remote arbitrary code execution: sandboxed code can obtain a host object proxy via Promise Symbol.species exploit, bypassing sanitizers and execute host code.

action required

Immediate action required

affected versions
patriksimek vm2
  • affected< 3.12.1
vendor says fixed in3.12.1

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