vm2: NodeVM builtin allowlist bypass via node:test.run() execArgv allows sandbox escape (Critical severity, CVE-2026-92948)
A critical-severity advisory for the npm package vm2 is fixed in version 3.11.7.
Key points
- vm2 (npm) has a critical flaw.
- Tracked as CVE-2026-92948.
- Version 3.11.7.
Maintainers of vm2, a package in the npm ecosystem, have published a critical-severity security advisory (CVE-2026-92948): vm2: NodeVM builtin allowlist bypass via node:test.run() execArgv allows sandbox escape.
At a glance
- Advisory
- GHSA-qhwx-74w5-xhxq
- CVE
- CVE-2026-92948
- Package
- vm2 (npm)
- Severity
- Critical
- Patched in
- 3.11.7
What is the issue?
The GitHub-reviewed advisory explains: Summary On Node.js 24 and newer, vm2 can expose the host node:test module to sandboxed NodeVM code when the embedder explicitly allows the node:test builtin. Sandbox code can reach that module through require('node:node:test') and call run() with attacker-controlled execArgv. node:test.run() starts a separate Node process for process-isolated test execution and forwards the supplied execArgv values to that process. Supplying --eval=<JavaScript therefore executes arbitrary JavaScript in an unrestricted host Node process, outside the NodeVM sandbox. The PoC confirms that direct sandbox imports of fs, child_process, module, and process remain denied before the spawned process imports host fs and writes a harmless marker. Affected versions and environment - Package: vm2 - Affected versions: =3.9.6, <=3.11.5 - Latest reproduced version: 3.11.5 - Reproduced runtime: Node.js v24.18.0 - Exact pa
Affected versions
| Ecosystem | Package | Vulnerable | Patched |
|---|---|---|---|
| npm | vm2 | >= 3.9.6, <= 3.11.6 | 3.11.7 |
The advisory lists a CVSS score of 9.9.
How to fix it
- Upgrade the affected package to the first patched version listed above.
- Rebuild and redeploy applications that bundle the vulnerable dependency.
- Run your dependency scanner (npm audit, pip-audit, Dependabot) to find transitive uses.
- Review the advisory references for workaround details if you cannot upgrade yet.
What to do and how to stay safe: CVE-2026-92948
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-92948?
CVE-2026-92948 is a security vulnerability in vm2 (npm).
Which version fixes CVE-2026-92948?
The fix is in version 3.11.7.
