OS Command Injection in 9router (CVE-2026-46339)
Summary
OS command injection in 9router (CVE-2026-46339). Successful exploitation can lead to full system takeover. Exploitable via POST /api/cli-tools/cowork-settings. Mitigation: upgrade to 0.4.37 or later.
Original description
The description as published by the source.
9Router is an AI router & token saver. From 0.4.30 until 0.4.37, 9Router's src/proxy.js middleware did not protect /api/cli-tools/* and /api/mcp/*, allowing unauthenticated registration of customPlugins through src/app/api/cli-tools/cowork-settings/route.js and command execution through the MCP bridge. This vulnerability is fixed in 0.4.37.
Source: GitHub Security Advisories (Global) 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-46339 has been found in 9router.
Attackers can target a specific entry point like POST /api/cli-tools/cowork-settings over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade 9router to 0.4.37 or later.
If unsure, ask your IT team or search "9router CVE-2026-46339" on the vendor's site.
CVE-2026-46339 (9router) — CWE-78 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/cli-tools/cowork-settings / GET /api/mcp/rev/sse / dashboardGuard / command
Patched: 0.4.37 — 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 POST /api/cli-tools/cowork-settings without authentication.
Check the vendor advisory for the affected versions of 9router. Attack surface: POST /api/cli-tools/cowork-settings / GET /api/mcp/rev/sse / dashboardGuard / command.
Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.
Update to 0.4.37.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/cli-tools/cowork-settings requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/cli-tools/cowork-settings' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/cli-tools/cowork-settingsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade 9router to 0.4.37ステージング環境で 0.4.37 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/cli-tools/cowork-settings on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com