Vulnerability in vm2 (CVE-2026-92936)
Summary
Vulnerability in vm2 (CVE-2026-92936). Risk of unauthorized operations or information disclosure. Exploitable via eval. Mitigation: upgrade to 3.11.7 or later.
Original description
The description as published by the source.
Summary
Attacker-controlled code can trigger a host-realm syntax error and read its stack through the vm2 bridge. Host-realm stack formatting bypasses the sandbox-side redaction, so the returned value exposes absolute paths from vm2, Node.js internals, and the embedding application. Default VM and NodeVM configurations are affected without requiring special options.
PoC
A default-configured VM runs attacker-supplied code. Calling eval with deliberately malformed source makes the host-side source transformer throw a SyntaxError; reading .stack on the caught error exposes the host call stack to the sandbox.
const { VM } = require("vm2");
console.log(new VM().run(`
var s; try { eval("@@@ catch") } catch (e) { s = e.stack }
s;
`));
Observed output
SyntaxError: Unexpected character '@'
at makeNiceSyntaxError (.../lib/transformer.js:41:16)
at transformer (.../lib/transformer.js:116:8)
at Object.transformAndCheck (.../lib/vm.js:76:14)
at Object.apply (.../lib/setup-sandbox.js:2585:16)
at VM.run (.../lib/vm.js:529:16)
The stack string returned to the sandbox contains absolute host paths for lib/transformer.js, lib/vm.js, lib/setup-sandbox.js, Node internals, and the embedding application's own source file.
Impact
Sandboxed code running under the default new VM() or new NodeVM() configuration can read absolute filesystem paths of the embedding application's source tree plus host function names, bypas…
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-92936 has been found in vm2.
Attackers can target a specific entry point like eval over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade vm2 to 3.11.7 or later.
If unsure, ask your IT team or search "vm2 CVE-2026-92936" on the vendor's site.
CVE-2026-92936 (vm2) — CWE-209 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: eval / SyntaxError
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-209) exists in vm2. Attackers reach the vulnerable code path via eval without authentication.
Check the vendor advisory for the affected versions of vm2. Attack surface: eval / SyntaxError.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
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
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com