Skip to content
Fencer Intel
high 7.2

CVE-2026-93604 json

vm2 3.11.8 Sandbox Escape via crypto.setFips

published 2mo ago modified last mo. also EUVD-2026-82899 , GHSA-x3v6-43hc-82mc

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository patriksimek/vm2. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
7.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm vm2 3.12.1
  • patriksimek vm2 3.12.1

Is CVE-2026-93604 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-93604 updated cvss 7.2

vm2: vm2: Sandbox escape via `crypto.setFips()` function

  • Red Hat Ansible Automation Platform 2.1 ansible-automation-platform/automation-portal 1791295379
    fixed: vendor fix RHSA-2026:80603
  • Red Hat Ansible Automation Platform 2.2 ansible-automation-platform/automation-portal 1791293780, ansible-automation-platform/bootc-automation-portal-rhel9 1791865660
    fixed: vendor fix RHSA-2026:80644
  • Red Hat Developer Hub 1.9 rhdh/rhdh-hub-rhel9 1793117813
    fixed: vendor fix RHSA-2026:91651
  • Red Hat Developer Hub 1.10 rhdh/rhdh-hub-rhel9 1791311495, rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend 1791242697, rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend 1791251282
    fixed: vendor fix RHSA-2026:76788
  • Red Hat Developer Hub 1.9 rhdh/rhdh-rhel9-operator 1793117972, rhdh/rhdh-operator-bundle 1793126835 Red Hat Developer Hub 1.10 rhdh/rhdh-rhel9-operator 1791219676, rhdh/rhdh-operator-bundle 1791315788, rhdh/rhdh-must-gather-rhel9 1788278523, rhdh/rhdh-rag-content-rhel9 1791168570, rhdh/red-hat-developer-hub-backstage-plugin-lightspeed 1791242743, rhdh/red-hat-developer-hub-backstage-plugin-orchestrator 1791250003, +3 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/patriksimek/vm2/security/advisories/GHSA-x3v6-43hc-82mc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L

Affected packages

ecosystem package affected fixed in
npm vm2
<=3.12.0
3.12.1

Affected products

  • patriksimek vm2

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of patriksimek/vm2 published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.