Vulnerability in vm2 (CVE-2026-92948)
Summary
Vulnerability in vm2 (CVE-2026-92948). 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
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= 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 path is not present on Node.js 22 because
module.builtinModulesdoes not expose the scheme-onlynode:testentry there - Configuration prerequisite:
require: {
builtin: ['node:test'],
external: false
}
The lower version boundary was tested directly: vm2@3.9.5 blocks require('node:node:test'), while vm2@3.9.6 permits the exploit path. Representative releases through 3.11.5 were also reproduced.
Root cause
The issue is a combination of builtin admission, generic host passthrough, and prefix normalization:
- On Node.js 24+,…
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-92948 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: 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-92948" on the vendor's site.
CVE-2026-92948 (vm2) — CWE-693 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: vm2 / NodeVM / execArgv / child_process
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-693) exists in vm2. Attackers reach the vulnerable code path via vm2.
Check the vendor advisory for the affected versions of vm2. Attack surface: vm2 / NodeVM / execArgv / child_process.
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