vm2 3.11.8 Sandbox Escape via crypto.setFips

Answer in brief

CVE-2026-93604 records a Unknown severity vulnerability in vm2 3.11.8 Sandbox Escape via crypto.setFips. The current sources do not mark it as known exploited. The current feed maps patriksimek/vm2 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 18, 2026Updated Sep 18, 2026Source checked Sep 18, 2026First seen by HOL Sep 18, 2026Material review Sep 18, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps patriksimek/vm2 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
patriksimek/vm2generic	>=0 <3.12.1	3.12.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for patriksimek/vm2.
Review the reported fix. Update patriksimek/vm2 to 3.12.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 18, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.