CVE-2026-92939: Process Control in patriksimek vm2
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.
AI Analysis
Technical Summary
The vm2 sandbox module versions 3.11.3 to 3.11.6 expose the host Node.js crypto module to the sandboxed NodeVM environment when the crypto builtin is allowed. Although the module is presented through a recursive read-only proxy, its callable exports execute with host process authority. This allows sandboxed JavaScript to invoke crypto.setEngine() with a path to a malicious native library, which the OpenSSL dynamic loader loads, executing native code in the host process before rejecting the engine symbol. This vulnerability enables sandbox escape and arbitrary native code execution without requiring access to other sensitive builtins like fs or child_process. The vulnerability is addressed in vm2 version 3.11.7.
Potential Impact
Exploitation of this vulnerability allows an attacker controlling sandboxed JavaScript code to escape the vm2 sandbox and execute arbitrary native code in the host process. This can lead to full compromise of the host environment running the vulnerable vm2 versions. The vulnerability does not require elevated privileges beyond sandbox access and does not depend on other Node.js builtins being exposed.
Mitigation Recommendations
A fix is available in vm2 version 3.11.7. Users should upgrade to version 3.11.7 or later to remediate this vulnerability. No other mitigations are indicated by the vendor advisory.
CVE-2026-92939: Process Control in patriksimek vm2
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.
CVSS v4.0
Score 9.4critical
Affected software
patriksimek
vm2
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vm2 sandbox module versions 3.11.3 to 3.11.6 expose the host Node.js crypto module to the sandboxed NodeVM environment when the crypto builtin is allowed. Although the module is presented through a recursive read-only proxy, its callable exports execute with host process authority. This allows sandboxed JavaScript to invoke crypto.setEngine() with a path to a malicious native library, which the OpenSSL dynamic loader loads, executing native code in the host process before rejecting the engine symbol. This vulnerability enables sandbox escape and arbitrary native code execution without requiring access to other sensitive builtins like fs or child_process. The vulnerability is addressed in vm2 version 3.11.7.
Potential Impact
Exploitation of this vulnerability allows an attacker controlling sandboxed JavaScript code to escape the vm2 sandbox and execute arbitrary native code in the host process. This can lead to full compromise of the host environment running the vulnerable vm2 versions. The vulnerability does not require elevated privileges beyond sandbox access and does not depend on other Node.js builtins being exposed.
Mitigation Recommendations
A fix is available in vm2 version 3.11.7. Users should upgrade to version 3.11.7 or later to remediate this vulnerability. No other mitigations are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-17T12:42:34.828Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aabfa1555bf5e2cf57f75e9
Added to database: 09/17/2026, 14:32:53 UTC
Last enriched: 09/17/2026, 14:46:42 UTC
Last updated: 09/18/2026, 01:10:07 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.