← Back
CVE-2026-49353
Vulnerability in 9router (CVE-2026-49353)
Summary
vulnerability in 9router (CVE-2026-49353). Risk of unauthorized operations or information disclosure. Exploitable via `GET /api/mcp/`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49353** has been found in 9router.
Attackers can target a specific entry point like `GET /api/mcp/` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "9router CVE-2026-49353" on the vendor's site.
CVE-2026-49353 (9router) — CWE-290 /
Attack surface: GET /api/mcp/ / POST /api/mcp/ / GET /api/mcp/browser/sse / `Host`
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.
❓ What is the problem
**A vulnerability** (CWE-290) exists in 9router. Attackers reach the vulnerable code path via `GET /api/mcp/` without authentication.
📍 Affected scope
9router — . Attack surface: GET /api/mcp/ / POST /api/mcp/ / GET /api/mcp/browser/sse / `Host`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /api/mcp/` 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /api/mcp/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /api/mcp/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against GET /api/mcp/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
9router
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- web https://github.com/decolua/9router/security/advisories/GHSA-6g2f-w7g3-77vf
- web https://github.com/decolua/9router/commit/5e1c1261368e06dced1cbc650684561b2c8844db
- web https://github.com/decolua/9router/commit/bb86808582067e4fc6f004508a919efb9970d1d5
- web https://github.com/advisories/GHSA-6g2f-w7g3-77vf