Path Traversal in vm2 (CVE-2026-92945)
Summary
Path traversal in vm2 (CVE-2026-92945). Risk of unauthorized operations or information disclosure. Exploitable via isPathAllowedForModule. Mitigation: upgrade to 3.11.7 or later.
Original description
The description as published by the source.
vm2 before 3.11.7 contains a module allowlist bypass vulnerability in isPathAllowedForModule that uses raw string prefix matching instead of boundary-anchored comparison. Attackers can reach non-allowlisted packages sharing a prefix with allowlisted modules by performing relative requires from allowlisted packages when transitive loading is disabled.
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-92945 has been found in vm2.
Attackers can target a specific entry point like isPathAllowedForModule over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade vm2 to 3.11.7 or later.
If unsure, ask your IT team or search "vm2 CVE-2026-92945" on the vendor's site.
CVE-2026-92945 (vm2) — CWE-22 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: isPathAllowedForModule / mod.path / startsWith / rem
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.
Path traversal (CWE-22) exists in vm2. Attackers reach the vulnerable code path via isPathAllowedForModule.
Check the vendor advisory for the affected versions of vm2. Attack surface: isPathAllowedForModule / mod.path / startsWith / rem.
Severity: Medium (CVSS 4.2/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
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com