Vulnerability in 9router (CVE-2026-56679)
Summary
Vulnerability in 9router (CVE-2026-56679). Risk of unauthorized operations or information disclosure. Exploitable via PATCH /api/settings. Mitigation: upgrade to 0.3.75 or later.
Original description
The description as published by the source.
9Router is an AI router & token saver. Prior to 0.5.4, the PATCH /api/settings endpoint writes the entire request body to persistent settings without a field whitelist, allowing an authenticated user to set security-critical fields such as requireLogin and disable authentication for the whole application, exposing protected routes such as /api/keys and /api/providers to unauthenticated access. This issue is reported as fixed in version 0.5.4.
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-56679 has been found in 9router.
Attackers can target a specific entry point like PATCH /api/settings over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade 9router to 0.3.75 or later.
If unsure, ask your IT team or search "9router CVE-2026-56679" on the vendor's site.
CVE-2026-56679 (9router) — CWE-915
Attack surface: PATCH /api/settings / POST /api/auth/login / GET /api/keys / requireLogin
Patched: 0.3.75 — 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-915) exists in 9router. Attackers reach the vulnerable code path via PATCH /api/settings.
Check the vendor advisory for the affected versions of 9router. Attack surface: PATCH /api/settings / POST /api/auth/login / GET /api/keys / requireLogin.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.3.75.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PATCH /api/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 'PATCH /api/settings' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /api/settingsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade 9router to 0.3.75ステージング環境で 0.3.75 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PATCH /api/settings on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com