OS Command Injection in 9router (CVE-2026-63732)
Summary
OS command injection in 9router (CVE-2026-63732). Successful exploitation can lead to full system takeover. Exploitable via Host header. Mitigation: upgrade to 0.4.60 or later.
Original description
The description as published by the source.
9router 0.4.59 (fixed in 0.4.60) contains a chain of vulnerabilities: a hardcoded default password (123456) that authenticates any fresh installation, a bypass of the LOCAL_ONLY network gate via a spoofed Host header, and unvalidated arguments passed to child_process.spawn() when registering MCP plugins. A remote, unauthenticated attacker can log in with the default credential, spoof the Host header to reach local-only routes, and register a malicious MCP plugin (e.g. node -e ) to achieve arbitrary code execution on the host operating system when the plugin's SSE endpoint is triggered.
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-63732 has been found in 9router.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade 9router to 0.4.60 or later.
If unsure, ask your IT team or search "9router CVE-2026-63732" on the vendor's site.
CVE-2026-63732 (9router) — CWE-78 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Host header
Patched: 0.4.60 — 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.
OS command injection (CWE-78) exists in 9router. Attackers reach the vulnerable code path via Host header.
Check the vendor advisory for the affected versions of 9router. Attack surface: Host header.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 0.4.60.
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 '9router' . 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 '9router' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
9routerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade 9router to 0.4.60ステージング環境で 0.4.60 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com