CVE-2026-55638: CWE-862: Missing Authorization in decolua 9router
9Router is an AI router & token saver. Prior to 0.5.2, 9router protects /v1, /v1beta, /api/v1, and /api/v1beta in src/dashboardGuard.js but omits /codex before next.config.mjs rewrites /codex/* to /api/v1/responses. A remote unauthenticated attacker can send requests to /codex/* to bypass the API-key gate and cause the server to make upstream provider calls using operator-stored LLM provider credentials. This issue is fixed in version 0.5.2.
AI Analysis
Technical Summary
9router, an AI router and token saver by decolua, protects several API endpoints (/v1, /v1beta, /api/v1, /api/v1beta) via src/dashboardGuard.js but omits protection for the /codex endpoint. Before version 0.5.2, requests to /codex/* bypass the API-key gate because next.config.mjs rewrites /codex/* to /api/v1/responses without enforcing authorization. This missing authorization (CWE-862) allows remote unauthenticated attackers to trigger upstream provider calls using operator credentials, potentially leading to information disclosure and service disruption. The vulnerability is addressed in version 0.5.2.
Potential Impact
An unauthenticated remote attacker can bypass API-key authorization by sending requests to the /codex endpoint, causing the server to make upstream calls with operator-stored LLM provider credentials. This can lead to unauthorized use of provider resources, potential data leakage (confidentiality impact), integrity issues, and high availability impact due to misuse of service calls. The CVSS 3.1 base score is 8.6 (High), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and impacts to confidentiality, integrity, and availability.
Mitigation Recommendations
This vulnerability is fixed in decolua 9router version 0.5.2. Users should upgrade to version 0.5.2 or later to remediate the issue. No other official remediation or temporary fixes are documented. Patch status is confirmed fixed in 0.5.2.
CVE-2026-55638: CWE-862: Missing Authorization in decolua 9router
Description
9Router is an AI router & token saver. Prior to 0.5.2, 9router protects /v1, /v1beta, /api/v1, and /api/v1beta in src/dashboardGuard.js but omits /codex before next.config.mjs rewrites /codex/* to /api/v1/responses. A remote unauthenticated attacker can send requests to /codex/* to bypass the API-key gate and cause the server to make upstream provider calls using operator-stored LLM provider credentials. This issue is fixed in version 0.5.2.
CVSS v3.1
Score 8.6high
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
9router, an AI router and token saver by decolua, protects several API endpoints (/v1, /v1beta, /api/v1, /api/v1beta) via src/dashboardGuard.js but omits protection for the /codex endpoint. Before version 0.5.2, requests to /codex/* bypass the API-key gate because next.config.mjs rewrites /codex/* to /api/v1/responses without enforcing authorization. This missing authorization (CWE-862) allows remote unauthenticated attackers to trigger upstream provider calls using operator credentials, potentially leading to information disclosure and service disruption. The vulnerability is addressed in version 0.5.2.
Potential Impact
An unauthenticated remote attacker can bypass API-key authorization by sending requests to the /codex endpoint, causing the server to make upstream calls with operator-stored LLM provider credentials. This can lead to unauthorized use of provider resources, potential data leakage (confidentiality impact), integrity issues, and high availability impact due to misuse of service calls. The CVSS 3.1 base score is 8.6 (High), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and impacts to confidentiality, integrity, and availability.
Mitigation Recommendations
This vulnerability is fixed in decolua 9router version 0.5.2. Users should upgrade to version 0.5.2 or later to remediate the issue. No other official remediation or temporary fixes are documented. Patch status is confirmed fixed in 0.5.2.
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: 6a511ed468715ace43d68971
Added to database: 07/10/2026, 16:33:24 UTC
Last enriched: 07/10/2026, 16:47:53 UTC
Last updated: 07/10/2026, 18:40:24 UTC
Views: 5
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.