Vulnerability in 9router (CVE-2026-56677)
Summary
Vulnerability in 9router (CVE-2026-56677). Data can be tampered with by attackers. Exploitable via POST /api/auth/oidc/test.
Original description
The description as published by the source.
Summary
A Server-Side Request Forgery (SSRF) vulnerability exists in the 9Router dashboard via the /api/auth/oidc/test endpoint. The application accepts a user-controlled URL string through the issuerUrl parameter and performs an outbound HTTP request without validating if the destination IP belongs to a restricted internal network range.
Notably, this endpoint can be accessed without active session authentication (Unauthenticated), allowing any remote actor with network visibility to the dashboard API endpoints to trigger outbound infrastructure connections.
Depending on the state and response of the internal port targeted, this flaw exhibits two distinct behaviors:
- Port Scanning / Blind SSRF (Non-OIDC structures): Probing internal ports that are closed or running non-HTTP/non-OIDC services (e.g., SSH, Databases) forces predictable application behavior changes (e.g., structural timeout or clear JSON parsing error messages like "Unexpected token..."), allowing internal network reconnaissance.
- Full Data Feed Manipulation (OIDC matching structures): If the targeted internal service responds with a valid OpenID configuration document structure, the backend successfully processes, parses, and reflects the internal properties back to the client, confirming partial data control.
Vulnerable Code Details
- Classification: VE-Class 4 — OIDC SSRF via issuerUrl (Unauthenticated)
- File Path:
src/app/api/auth/oidc/test/route.js - **Vulnerabl…
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-56677 has been found in 9router.
Attackers can target a specific entry point like POST /api/auth/oidc/test over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "9router CVE-2026-56677" on the vendor's site.
CVE-2026-56677 (9router) — CWE-306 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/auth/oidc/test / Cookie header / issuerUrl / token_endpoint
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-306) exists in 9router. Attackers reach the vulnerable code path via POST /api/auth/oidc/test without authentication.
Check the vendor advisory for the affected versions of 9router. Attack surface: POST /api/auth/oidc/test / Cookie header / issuerUrl / token_endpoint.
Severity: High (CVSS 8.6/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
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/auth/oidc/test 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/auth/oidc/test' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/auth/oidc/testへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/auth/oidc/test on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com