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.
References
Configurations
No configuration.
History
17 Sep 2026, 15:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffx - |
17 Sep 2026, 14:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-17 14:17
Updated : 2026-09-17 15:17
NVD link : CVE-2026-92939
Mitre link : CVE-2026-92939
CVE.ORG link : CVE-2026-92939
JSON object : View
Products Affected
No product.
CWE
CWE-114
Process Control
