Vulnerability · Published Sep 17, 2026 · Assigned by VulnCheck

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

Critical 9.9

In plain English

A critical-severity security flaw in vm2 from patriksimek. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 50% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)9.9Critical

Exploit odds (30 days)0.6%top 50.3% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official 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 packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	vm2	3.11.7	GHSA-46pr-c5wc-xffx

Affected products (as reported)

Vendor	Product	Versions
patriksimek	vm2	3.11.3 – before 3.11.7

Weakness: CWE-114 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

References

GitHub Security Advisory (GHSA-46pr-c5wc-xffx) vendor-advisory
VulnCheck Advisory: vm2 3.11.3 through 3.11.6 Native Code Execution via crypto.setEngine third-party-advisory