Code Injection in 9router (CVE-2026-108593)
Summary
Code injection in 9router (CVE-2026-108593). Successful exploitation can lead to full system takeover. Exploitable via POST /api/cli-tools/hermes-settings.
Original description
The description as published by the source.
9router 0.4.1 through 0.5.99 contains a configuration injection vulnerability in the POST /api/cli-tools/hermes-settings endpoint that allows authenticated dashboard users to inject arbitrary keys into the Hermes Agent config.yaml file. Attackers can submit a baseUrl containing double quotes and newlines to add hooks_auto_accept and a hooks.post_llm_call shell command, which Hermes Agent executes without approval after an LLM call.
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-108593 has been found in 9router.
Attackers can target a specific entry point like POST /api/cli-tools/hermes-settings over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 6.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "9router CVE-2026-108593" on the vendor's site.
CVE-2026-108593 (9router) — CWE-94 / CVSS v3 6.4
Attack vector: remote (network-reachable)
Attack surface: POST /api/cli-tools/hermes-settings
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.
Arbitrary code execution (CWE-94) exists in 9router. Attackers reach the vulnerable code path via POST /api/cli-tools/hermes-settings.
Check the vendor advisory for the affected versions of 9router. Attack surface: POST /api/cli-tools/hermes-settings.
Severity: Medium (CVSS 6.4/10). Successful exploitation can lead to full system takeover.
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/cli-tools/hermes-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 'POST /api/cli-tools/hermes-settings' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/cli-tools/hermes-settingsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/cli-tools/hermes-settings on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web hackmd.io
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com