vm2 is a widely used Node.js sandbox library; this RCE sandbox-escape affects many apps and services that execute untrusted JS, posing broad enterprise impact and supply-chain risk.
CVE-2026-92934
vm2 sandbox escape RCE via crafted AggregateError cycle detection.
Is CVE-2026-92934 being exploited?
Not confirmed. CVE-2026-92934 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-92934?
CVE-2026-92934 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-92934?
Yes. A fix has been recorded for CVE-2026-92934. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-92934 affect?
CVE-2026-92934 affects vm2 < 3.11.8, Node.js applications using vm2 sandbox, 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-92934?
Upgrade vm2 to >=3.11.8 or remove/mitigate use; audit code paths executing untrusted JS.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution and process info disclosure by escaping vm2 sandbox using a cycle-detection bypass in AggregateError handling.
Immediate action required
- affected< 3.11.8
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.