Privilege Escalation in vm2 (CVE-2026-92957)
Summary
Vulnerability in vm2 (CVE-2026-92957). Successful exploitation can lead to full system takeover. Exploitable via child_process. Mitigation: upgrade to 3.11.7 or later.
Original description
The description as published by the source.
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:
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
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
lib/builtin.jsmakeBuiltinsFromLegacyOptions- wildcard builtin expansion
- exact negative entry check:
builtins.indexOf(\-${name}`)` addDefaultBuiltin
lib/resolver.jsResolver.resolve
lib/setup-node-sandbox.jsrequireImplnode:prefix stripping before builtin load
Root Cause
lib/setup-node-sandbox.js strips the node: prefix from resolved builtin filenames before loading the builtin:
if (localStringPrototypeStartsWith(filename, 'node:')) {
id = localSt…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-92957 has been found in vm2.
Attackers can target a specific entry point like child_process over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade vm2 to 3.11.7 or later.
If unsure, ask your IT team or search "vm2 CVE-2026-92957" on the vendor's site.
CVE-2026-92957 (vm2) — CWE-269 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: child_process / execSync / spawn / makeBuiltinsFromLegacyOptions
Patched: 3.11.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in vm2. Attackers reach the vulnerable code path via child_process.
Check the vendor advisory for the affected versions of vm2. Attack surface: child_process / execSync / spawn / makeBuiltinsFromLegacyOptions.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 3.11.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'vm2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'vm2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
vm2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade vm2 to 3.11.7ステージング環境で 3.11.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web vulncheck.com
- web github.com
- web github.com
- web github.com