Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Sat, 19 Sep 2026 00:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Patriksimek
Patriksimek vm2 |
|
| Vendors & Products |
Patriksimek
Patriksimek vm2 |
Fri, 18 Sep 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 18 Sep 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | vm2 through 3.12.0 exposes Node.js's crypto.setFips() function to untrusted guest code when an embedder explicitly allowlists the crypto builtin for a NodeVM (require.builtin: ['crypto']). The builtin sanitizer (sanitizeCryptoModule in lib/builtin.js) replaces crypto.setEngine but leaves crypto.setFips callable, and the readonly wrapper used to expose the host module does not localize side effects of forwarded host functions. Guest code can therefore call crypto.setFips() to change the FIPS mode of the entire host process; the modified mode is subsequently observed by trusted host code (crypto.getFips() changed from 0 to 1 in the reported test), crossing the NodeVM isolation boundary. Fixed in vm2 3.12.1. | |
| Title | vm2 3.11.8 Sandbox Escape via crypto.setFips | |
| First Time appeared |
Vm2 Project
Vm2 Project vm2 |
|
| Weaknesses | CWE-284 | |
| CPEs | cpe:2.3:a:vm2_project:vm2:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Vm2 Project
Vm2 Project vm2 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-09-18T13:55:28.976Z
Reserved: 2026-09-18T11:00:32.756Z
Link: CVE-2026-93604
Updated: 2026-09-18T13:55:13.575Z
Status : Deferred
Published: 2026-09-18T14:19:12.167
Modified: 2026-09-18T14:19:12.287
Link: CVE-2026-93604
No data.
OpenCVE Enrichment
Updated: 2026-09-19T00:30:16Z