Host cryptographic-policy modification via unsanitized crypto.setFips
Published Sep 18, 2026 · Updated Sep 18, 2026
Improper access control in vm2 through 3.12.0 allows attackers to alter host cryptographic policy from a NodeVM guest. The sanitizeCryptoModule function leaves crypto.setFips callable, while the readonly wrapper forwards the host function and its process-wide side effects. Exploitation requires an embedder to allowlist the crypto builtin and a Node/OpenSSL build with functional FIPS support; affected host cryptographic operations can subsequently fail.
Summary
What happened
Improper access control in vm2 through 3.12.0 allows attackers to alter host cryptographic policy from a NodeVM guest. The sanitizeCryptoModule function leaves crypto.setFips callable, while the readonly wrapper forwards the host function and its process-wide side effects. Exploitation requires an embedder to allowlist the crypto builtin and a Node/OpenSSL build with functional FIPS support; affected host cryptographic operations can subsequently fail.
The record
- CVE
- CVE-2026-93604
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- Patrik Simek
- Product
- vm2
- Classifications
- CWE-284, CWE-693
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=0 <3.12.1
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.setFips proof of conceptproof of concept · demonstrated
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.
Get started