Quick answers
- Is CVE-2026-93604 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93604 being exploited in the wild.
- How severe is CVE-2026-93604?
- High severity, with a CVSS score of 7.2, published 18 September 2026.
- Which products and versions are affected?
- Patrick Simek vm2 through 3.12.0.
- Is there a fix for CVE-2026-93604?
- A patch was published on 2026-09-18: vm2 3.12.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93604 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-93604?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an improper access control vulnerability (CWE-284) in vm2's builtin module sanitizer. The sanitizeCryptoModule function in lib/builtin.js replaces crypto.setEngine but fails to neutralize crypto.setFips(), which is a process-wide state mutation. Although the module is exposed through a readonly wrapper that prevents property replacement, the wrapper does not localize side effects of forwarded host functions. An attacker who can supply JavaScript to a NodeVM with require.builtin: ['crypto'] configured can call crypto.setFips(1) to enable FIPS mode on the host process, which is then observed by trusted host code via crypto.getFips(). No authentication, network access, or user interaction is required beyond code execution within the NodeVM itself. The vulnerability is fixed in vm2 3.12.1.
Affected products
- Patrick Simek vm2 through 3.12.0
Timeline
- 2026-09-18: disclosed
- 2026-09-18: patched: vm2 3.12.1 released