CVE-2026-92948
- Source
- https://cve.org/CVERecord?id=CVE-2026-92948
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-92948.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-92948
- Aliases
-
- GHSA-qhwx-74w5-xhxq
- Published
- 2026-09-17T13:46:08Z
- Modified
- 2026-09-19T11:30:58Z
- Severity
-
- 9.4 (Critical) CVSS_V4 - 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 CVSS Calculator
- Summary
- vm2 3.9.6 through 3.11.5 Sandbox Escape via node:test
- Details
-
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= therefore executes arbitrary JavaScript in an unrestricted host Node process outside the NodeVM sandbox. Fixed in vm2 3.11.7.
- Database specific
{ "cna_assigner": "VulnCheck", "cwe_ids": [ "CWE-693" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/92xxx/CVE-2026-92948.json" }- References