patriksimek vm2 up to 3.12.0 Builtin Sanitizer lib/builtin.js crypto.setFips isolation

Summaryinfo

A vulnerability was found in patriksimek vm2 up to 3.12.0. It has been classified as critical. This affects the function crypto.setFips of the file lib/builtin.js of the component Builtin Sanitizer. This manipulation causes isolation. This vulnerability appears as CVE-2026-93604. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical was found in patriksimek vm2 up to 3.12.0. Affected by this vulnerability is the function crypto.setFips of the file lib/builtin.js of the component Builtin Sanitizer. The manipulation with an unknown input leads to a isolation vulnerability. The CWE definition for the vulnerability is CWE-653. The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions. As an impact it is known to affect integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-93604 since 09/18/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 3.12.1 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• patriksimek

Name

• vm2

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 3.8
• 3.9
• 3.10
• 3.11
• 3.12.0

Website

• Product: https://github.com/patriksimek/vm2/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion