PoC Monitor
← All CVEs
CVE-2026-92939published 17 Sep 2026 13:46 UTCData: JSON · API

Patriksimek vm2

vm2 3.11.3 through 3.11.6 Native Code Execution via crypto.setEngine

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.9critical · scored by CNA · CWE-114
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

patriksimek vm2
  • >= 3.11.3, < 3.11.7

Fixed in 3.11.7

Mitigation

Upgrade vm2 to 3.11.7 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published17 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.