Widespread Node.js sandbox library vm2; RCE sandbox escape in many applications handling untrusted code — high-impact and newsworthy.
CVE-2026-92939
vm2 sandbox escape enabling native code execution via crypto.setEngine().
Is CVE-2026-92939 being exploited?
Not confirmed. CVE-2026-92939 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-92939?
CVE-2026-92939 is rated Critical with a CVSS score of 9.4. 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-92939?
Yes. A fix has been recorded for CVE-2026-92939. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-92939 affect?
CVE-2026-92939 affects vm2 3.11.3 - 3.11.6, Node.js apps using vm2 with crypto builtin allowed, Environments running untrusted plugins or code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-92939?
Upgrade vm2 to >=3.11.7, disable/deny crypto builtin for untrusted sandboxes, audit and rotate secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandboxed JS can load attacker native libraries via crypto.setEngine(), causing host-process native code execution and full RCE.
Immediate action required
- affected>= 3.11.3 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.