CVE-2026-92939

published 17 Sep 2026 · updated 17 Sep 2026

vm2 3.11.3 through 3.11.6 Native Code Execution via crypto.setEngine

9.9CriticalCVSS 9.9EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.11.7.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
patriksimek>=3.11.3 <3.11.73.11.7

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-92939 severity on Zeptric[![CVE-2026-92939](https://zeptric.io/badge/cve/CVE-2026-92939.svg)](https://zeptric.io/cve/CVE-2026-92939)