Native code execution via unchecked crypto.setEngine calls
Published Sep 17, 2026 · Updated Sep 17, 2026
Sandbox escape in vm2 3.11.3 through 3.11.6 allows attackers to execute native code through NodeVM's crypto builtin. The builtin loader's read-only proxy forwards crypto.setEngine() calls with host authority, allowing library constructors to run before OpenSSL validates the supplied file. Exploitation requires crypto access, OpenSSL engine support, and an attacker-supplied native library already on disk; execution inherits the host process's privileges.
Summary
What happened
Sandbox escape in vm2 3.11.3 through 3.11.6 allows attackers to execute native code through NodeVM's crypto builtin. The builtin loader's read-only proxy forwards crypto.setEngine() calls with host authority, allowing library constructors to run before OpenSSL validates the supplied file. Exploitation requires crypto access, OpenSSL engine support, and an attacker-supplied native library already on disk; execution inherits the host process's privileges.
The record
- CVE
- CVE-2026-92939
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Patrik Simek
- Product
- vm2
- Classifications
- CWE-114, T1129
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.11.3 <3.11.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- Upstream crypto.setEngine native-library regression reproductionproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us