CVE-2026-92939: vm2 3.11.3 through 3.11.6 Native Code Execution via crypto.setEngine

Severity: critical (CVSS 9.9 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.6% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-09-17 · updated 2026-09-17
Weakness: CWE-114

Description

vm2 3.11.3 through 3.11.6 exposes the host Node.js crypto module to a NodeVM sandbox when the crypto builtin is allowed. The module is presented via a recursive read-only proxy, but its callable exports still execute with host-process authority. Sandboxed JavaScript can therefore call crypto.setEngine() with a filesystem path to an attacker-supplied native library (for example, one bundled in an untrusted plugin package already written to disk); OpenSSL asks the operating-system dynamic loader to load the file, and the library's constructor executes native code in the host process before engine-symbol validation rejects it. Exploitation requires only the crypto builtin and does not require fs, process, module, child_process, worker_threads, vm, or inspector access, resulting in a sandbox escape and arbitrary native code execution. Fixed in 3.11.7.

Affected products

patriksimek vm2: from 3.11.3 before 3.11.7 — fixed in 3.11.7

How to fix

Upgrade to a fixed version: patriksimek vm2 3.11.7. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-92939 or the next vulnerability affects your stack