Decolua 9router
9router: Unauthenticated `/v1` proxy access via `Host`-header spoofing → open AI relay + SSRF
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.5.2
Fixed in 0.5.2
Mitigation
Upgrade 9router to 0.5.2 or later.
References
- Vendor advisory github.com/decolua/9router/security/advisories…
- Patch github.com/decolua/9router/commit/b282f0554972…
- Release notes github.com/decolua/9router/releases/tag/v0.5.2
Timeline
Days relative to CVE publicationFirst public PoC 130 days after publication; not in CISA KEV. First PoC: nuclei template: 9router < 0.5.2 - Authentication Bypass via Host Header Spoofing (nuclei template, 17 Nov 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: 9router < 0.5.2 - Authentication Bypass via Host Header Spoofing | 17 Nov 2026 | 18 Nov 2026 |