9Router is an AI router & token saver. Prior to 0.5.2, 9router determines whether a /v1 LLM proxy request is local by reading the client-controlled Host header, allowing a remote unauthenticated attacker to send Host: localhost and bypass API-key authentication. In the default configuration, this exposes the /v1 proxy to upstream provider calls using stored provider credentials and allows /v1/search with the searxng provider_options.baseUrl parameter to drive server-side requests to internal or cloud-metadata hosts. This issue is fixed in version 0.5.2.
CVE-2026-55641
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(low)
- EPSS
- —
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (3)
Auto-updated Jul 10, 2026Unauthenticated `/v1` proxy access in [email protected] via `Host`-header spoofing → open AI relay + SSRF · Advisory · decolua/9router · GitHub
https://github.com/decolua/9router/security/advisories/GHSA-86m2-fcxq-5q7cfeat: Combo Fusion + Capacity auto-switch, Kiro API-key, Claude auto-ping & 429 throttle version 0.5.2
Patch available: decolua/9router v0.5.2
https://github.com/decolua/9router/releases/tag/v0.5.2commit b282f0554972 (decolua/9router)
Patch available: decolua/9router v0.5.2 (contains commit b282f0554972)
https://github.com/decolua/9router/commit/b282f0554972ea35281520738759d76abcd0b0b3Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-11 14:34 UTCEG score recompute
- 2026-07-11 03:34 UTCEG score recompute
- 2026-07-10 16:34 UTCEG score recompute
- 2026-07-10 16:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(4)
What is CVE-2026-55641?
When was CVE-2026-55641 disclosed?
What is the CVSS score of CVE-2026-55641?
How do I remediate CVE-2026-55641?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55641
Is Your Infrastructure Affected by CVE-2026-55641?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.