CVE-2026-92939 — vm2 3.11.3 through 3.11.6 exposes the host Node.js crypto module to a NodeVM sandbox when…¶
Key facts
CVE-2026-92939 is a Critical (9.9) vulnerability: vm2 3.11.3 through 3.11.6 exposes the host Node.js crypto module to a NodeVM sandbox when…. This entry ships a detection-only PoC and a Docker test lab.
| CVE | CVE-2026-92939 |
| Severity | Critical (9.9) |
| Detection / prevention | — |
| PoC | poc.py |
| Source | 2026/CVE-2026-92939/ |
Details¶
English | 한국어
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.
Vulnerability Details¶
| Property | Value |
|---|---|
| CVE ID | CVE-2026-92939 |
| CVSS Score | 9.9 |
Proof of Concept¶
Download¶
# Download PoC script
curl -O https://raw.githubusercontent.com/fankh/vulnerability-poc/main/2026/CVE-2026-92939/poc.py
Usage¶
# Run PoC against target
python3 poc.py --target <TARGET_URL>
# With authentication
python3 poc.py --target <TARGET_URL> --username <USER> --password <PASS>
⚠️ Warning: This PoC is for authorized security testing only. It uses detection-only techniques and does not exploit or damage target systems.
Test Lab¶
This repository includes a Docker-based test environment with both vulnerable and patched applications.
Quick Start¶
# Clone and navigate to CVE directory
cd CVE-2026-92939
# Start both applications
docker-compose up -d
# Run tests
./run-tests.sh # Linux/Mac
./run-tests.ps1 # Windows PowerShell
Application Endpoints¶
| Application | URL | Status |
|---|---|---|
| Vulnerable App | http://localhost:8080 | Shows vulnerability |
| Patched App | http://localhost:8081 | Demonstrates fix |
Directory Structure¶
├── README.md # English documentation
├── README_KO.md # Korean documentation
├── poc.py # PoC detection script
├── docker-compose.yml # Container orchestration
├── run-tests.sh # Linux/Mac test runner
├── run-tests.ps1 # Windows test runner
├── vulnerable-app/ # Vulnerable version
│ ├── app.py
│ ├── Dockerfile
│ └── requirements.txt
└── patched-app/ # Fixed version
├── app.py
├── Dockerfile
└── requirements.txt
References¶
- https://github.com/patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffx
- https://www.vulncheck.com/advisories/vm2-3.11.3-through-3.11.6-native-code-execution-via-crypto-setengine
- https://github.com/patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffx
Generated by PoC Generator on 2026-09-18T07:40:43.473355783
Frequently asked questions¶
What is CVE-2026-92939?¶
CVE-2026-92939 is a Critical (9.9) vulnerability: vm2 3.11.3 through 3.11.6 exposes the host Node.js crypto module to a NodeVM sandbox when…. This entry ships a detection-only PoC and a Docker test lab.
How do I detect CVE-2026-92939?¶
Run the detection-only PoC included with this entry against your Docker test lab to confirm whether a target is affected; pair it with your own IDS logging.
How do I block or mitigate CVE-2026-92939?¶
Upgrade to a fixed version per the vendor advisory; the NVD record lists the affected versions. Use the included PoC to verify your remediation.
For authorized security testing and research only. See the full source and NVD record.