Skip to content
Fencer Vulns
critical 9.9

CVE-2026-92948 json

vm2 3.9.6 through 3.11.5 Sandbox Escape via node:test

published 2026-09-17 53 d ago modified 2026-10-01 38 d ago also GHSA-qhwx-74w5-xhxq , EUVD-2026-81597

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

Summary

vm2 versions >= 3.9.6 and <= 3.11.6 are affected by a NodeVM builtin allowlist bypass that permits a sandbox escape on Node.js 24 and newer when the embedder explicitly allows the node:test builtin (e.g. require: { builtin: ['node:test'] }). On Node.js 24+, module.builtinModules exposes the scheme-only key node:test, which is not covered by vm2's family-based DANGEROUS_BUILTINS protection, so it is stored in the generic host-passthrough loader. Because requireImpl() in lib/setup-node-sandbox.js strips a single 'node:' prefix before the builtin lookup, sandbox code calling require('node:node:test') resolves to the stored node:test key and receives a readonly proxy to the host module. Calls to node:test.run() are forwarded to the host implementation, which spawns a separate Node process for process-isolated test execution and passes through attacker-controlled execArgv values; supplying --eval=<JavaScript> therefore executes arbitrary JavaScript in an unrestricted host Node process outside the NodeVM sandbox. Fixed in vm2 3.11.7.

Patch / fix

  • npm vm2 3.11.7
  • patriksimek vm2 3.11.7

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-92948 updated cvss 9.9

vm2: vm2 3.9.6 through 3.11.5 Sandbox Escape via node:test

  • 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
no
Technical impact
total
Assessed
51 d ago

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/patriksimek/vm2/security/advisories/GHSA-qhwx-74w5-xhxq referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 9.4 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA 4.0 9.4 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm vm2
>=3.9.6, <3.11.7
3.11.7

Affected products

  • patriksimek vm2

Classification

Weakness
  • CWE-693 Protection Mechanism Failure

References

Sources

Fencer Vulns 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.