9Router
9Router: Authentication Bypass in Public LLM API via Spoofable X-9r-Real-Ip Header
9Router is an AI router & token saver. Prior to 0.5.6, 9Router deployments that allow requests to reach Next.js without the sanitizing custom-server.js wrapper trust the client-supplied X-9r-Real-Ip header in src/dashboardGuard.js when isLocalRequest decides whether canAccessPublicLlmApi may skip API-key validation for /api/v1/* routes. A remote unauthenticated attacker can set X-9r-Real-Ip to 127.0.0.1 and be classified as a local client, including on the verified GET /api/v1/models route. This permits unauthorized use of the instance owner's configured LLM providers, consumption of paid credits, and enumeration of configured providers and models. This issue is fixed in version 0.5.6.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.5.6
Fixed in 0.5.6
Mitigation
Upgrade 9router to 0.5.6 or later.
References
- Vendor advisory github.com/decolua/9router/security/advisories…
- Patch github.com/decolua/9router/commit/efd20be8d81e…
- Release notes github.com/decolua/9router/releases/tag/v0.5.6
Timeline
Days relative to CVE publicationFirst public PoC 11 h after publication; not in CISA KEV. First PoC: nuclei template: 9router <=0.5.4 - Authentication Bypass (nuclei template, 23 Sep 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.4 - Authentication Bypass | 23 Sep 2026 | 14 Nov 2026 |