Vulnerability in vm2 (CVE-2026-92950)
Summary
Vulnerability in vm2 (CVE-2026-92950). Successful exploitation can lead to full system takeover. Exploitable via vm2. Mitigation: upgrade to 3.11.7 or later.
Original description
The description as published by the source.
Summary
The vm2 command-line tool installed by npm install -g vm2 and documented in the README's "CLI" section runs the supplied script under NodeVM with require:{external:true} and no root / context / builtin configured. With these defaults the resolver loads every relative or absolute require() target through the host require() function, executing the attacker's module body in the host Node.js process before the result is ever proxied back into the sandbox. A single attacker-controlled file passed to vm2 ./script.js can call require(__filename) to re-execute itself in host realm and reach fs, child_process, etc. The documented sandbox runner is therefore equivalent to node ./script.js. No additional files, flags, or user interaction are required.
Details
The vulnerability lets a malicious sandboxed script - the file argument to the documented vm2 CLI - execute arbitrary code in the host Node.js process, crossing the sandbox → host boundary that vm2 is meant to enforce.
Vulnerable code path
- Source -
bin/vm2:3→lib/cli.js:7-18.process.argv[2]is the
attacker-authored script path. The CLI invokes:
WithoutNodeVM.file(path, { verbose: true, require: { external: true } });require.root,require.context, norrequire.builtin. - Hop -
lib/nodevm.js:618-636.NodeVM.filereads the file and calls
new NodeVM(options).run(body, resolvedFilename). - Hop - `lib/nodev…
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-92950 has been found in vm2.
Attackers can target a specific entry point like vm2 over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.6/10.
What to do: upgrade vm2 to 3.11.7 or later.
If unsure, ask your IT team or search "vm2 CVE-2026-92950" on the vendor's site.
CVE-2026-92950 (vm2) — CWE-453 / CVSS v3 8.6
Attack vector: local / unauthenticated
Attack surface: vm2 / NodeVM / root / context
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-453) exists in vm2. Attackers reach the vulnerable code path via vm2 without authentication.
Check the vendor advisory for the affected versions of vm2. Attack surface: vm2 / NodeVM / root / context.
Severity: High (CVSS 8.6/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