vm2: NodeVM node:-prefixed negative builtin deny bypass exposes child_process (Critical severity, CVE-2026-92957)
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-92957.
- Version 3.11.7.
Maintainers of vm2, a package in the npm ecosystem, have published a critical-severity security advisory (CVE-2026-92957): vm2: NodeVM node:-prefixed negative builtin deny bypass exposes child_process.
At a glance
- Advisory
- GHSA-8686-vhfx-7r3j
- CVE
- CVE-2026-92957
- Package
- vm2 (npm)
- Severity
- Critical
- Patched in
- 3.11.7
What is the issue?
The GitHub-reviewed advisory explains: Summary NodeVM normalizes node:-prefixed builtin specifiers during require() resolution, but it does not normalize user-provided negative builtin entries in wildcard policy. As a result, this configuration: js new NodeVM({ require: { builtin: ['', '-node:child_process'] } }); does not deny the canonical child_process builtin. Sandboxed code can require both child_process and node:child_process, and receives the host module with process-spawning APIs such as execSync and spawn. The safe proof below only checks module and function reachability. It does not execute any OS command. Affected Mode NodeVM. Affected Configuration js new NodeVM({ require: { builtin: ['', '-node:child_process'] } }); This affects users who deny builtins using their node:-prefixed spelling, expecting -node:child_process to deny require('node:child_process') and require('child_process'). Affected Files / Functions -
Affected versions
| Ecosystem | Package | Vulnerable | Patched |
|---|---|---|---|
| npm | vm2 | <= 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-92957
- 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-92957?
CVE-2026-92957 is a security vulnerability in vm2 (npm).
Which version fixes CVE-2026-92957?
The fix is in version 3.11.7.
