Authentication Bypass in 9router (CVE-2026-56675)
Summary
Authentication bypass in 9router (CVE-2026-56675). Risk of unauthorized operations or information disclosure. Exploitable via Origin. Mitigation: upgrade to 0.5.2 or later.
Original description
The description as published by the source.
9Router is an AI router & token saver. Prior to 0.5.2, 9router treats loopback requests as trusted and allows /v1/* access without an API key, so a same-host reverse proxy that forwards public traffic to the backend through 127.0.0.1 causes src/dashboardGuard.js to misclassify external requests as local. A remote unauthenticated attacker can access /v1 APIs such as /v1/models and may abuse configured upstream provider credentials through /v1 proxy endpoints depending on enabled providers. This issue is fixed in version 0.5.2.
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-56675 has been found in 9router.
Attackers can target a specific entry point like Origin over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 8.3/10.
What to do: upgrade 9router to 0.5.2 or later.
If unsure, ask your IT team or search "9router CVE-2026-56675" on the vendor's site.
CVE-2026-56675 (9router) — CWE-287 / CVSS v3 8.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Origin / b282f05 / localhost
Patched: 0.5.2 — 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.
Authentication bypass (CWE-287) exists in 9router. Attackers reach the vulnerable code path via Origin without authentication.
Check the vendor advisory for the affected versions of 9router. Attack surface: Origin / b282f05 / localhost.
Severity: High (CVSS 8.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.5.2.
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.5.2ステージング環境で 0.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com