CVE-2026-55641: CWE-290: Authentication Bypass by Spoofing in decolua 9router
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.
AI Analysis
Technical Summary
In decolua 9router versions before 0.5.2, the application relies on the client-supplied Host header to determine if a /v1 LLM proxy request is local. This design flaw allows a remote unauthenticated attacker to spoof the Host header as 'localhost' and bypass API-key authentication. Consequently, the attacker can access the /v1 proxy endpoint, which in the default configuration exposes upstream provider calls using stored credentials. Additionally, the /v1/search endpoint with the searxng provider_options.baseUrl parameter can be abused to perform server-side requests to internal or cloud metadata hosts. The vulnerability is addressed by updating to version 0.5.2.
Potential Impact
The vulnerability enables remote unauthenticated attackers to bypass authentication controls and access sensitive API endpoints. This can lead to unauthorized use of stored provider credentials for upstream calls and server-side request forgery to internal or cloud metadata services. The confidentiality of sensitive data is at high risk, while integrity impact is low and availability is not affected.
Mitigation Recommendations
Upgrade decolua 9router to version 0.5.2 or later, where this authentication bypass vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.
CVE-2026-55641: CWE-290: Authentication Bypass by Spoofing in decolua 9router
Description
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.
CVSS v3.1
Score 8.2high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In decolua 9router versions before 0.5.2, the application relies on the client-supplied Host header to determine if a /v1 LLM proxy request is local. This design flaw allows a remote unauthenticated attacker to spoof the Host header as 'localhost' and bypass API-key authentication. Consequently, the attacker can access the /v1 proxy endpoint, which in the default configuration exposes upstream provider calls using stored credentials. Additionally, the /v1/search endpoint with the searxng provider_options.baseUrl parameter can be abused to perform server-side requests to internal or cloud metadata hosts. The vulnerability is addressed by updating to version 0.5.2.
Potential Impact
The vulnerability enables remote unauthenticated attackers to bypass authentication controls and access sensitive API endpoints. This can lead to unauthorized use of stored provider credentials for upstream calls and server-side request forgery to internal or cloud metadata services. The confidentiality of sensitive data is at high risk, while integrity impact is low and availability is not affected.
Mitigation Recommendations
Upgrade decolua 9router to version 0.5.2 or later, where this authentication bypass vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T23:52:12.057Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a511ed468715ace43d68976
Added to database: 07/10/2026, 16:33:24 UTC
Last enriched: 07/10/2026, 16:47:47 UTC
Last updated: 07/10/2026, 19:33:04 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.