Vulnerability in 9router (CVE-2026-56678)
Summary
Vulnerability in 9router (CVE-2026-56678). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/oauth/kiro/api-key. Mitigation: upgrade to 0.5.6 or later.
Original description
The description as published by the source.
9Router is an AI router & token saver. Prior to 0.5.6, the Kiro API-key validation endpoint POST /api/oauth/kiro/api-key builds an upstream URL using a user-controlled region value, allowing an authenticated attacker to supply a crafted region such as kiro-canary.local:8443# and cause 9Router to send the Kiro validation request to an attacker-controlled host while forwarding the submitted Kiro API key as an Authorization header. This issue is fixed in version 0.5.6.
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-56678 has been found in 9router.
Attackers can target a specific entry point like POST /api/oauth/kiro/api-key over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: upgrade 9router to 0.5.6 or later.
If unsure, ask your IT team or search "9router CVE-2026-56678" on the vendor's site.
CVE-2026-56678 (9router) — CWE-20 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/oauth/kiro/api-key / Authorization header / region / NODE_EXTRA_CA_CERTS
Patched: 0.5.6 — 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-20) exists in 9router. Attackers reach the vulnerable code path via POST /api/oauth/kiro/api-key.
Check the vendor advisory for the affected versions of 9router. Attack surface: POST /api/oauth/kiro/api-key / Authorization header / region / NODE_EXTRA_CA_CERTS.
Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.5.6.
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/oauth/kiro/api-key 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/oauth/kiro/api-key' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/oauth/kiro/api-keyへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade 9router to 0.5.6ステージング環境で 0.5.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/oauth/kiro/api-key on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com