CVE-2026-62327 in 9Router
Summary
by MITRE • 07/14/2026
9Router through version 0.4.41 contain an unauthenticated information disclosure vulnerability that allows remote attackers to retrieve plaintext API keys for all connected AI provider accounts by sending a single unauthenticated request to the /api/usage/stats endpoint. Attackers can exploit the missing authentication middleware on the Next.js API route to obtain full API key strings alongside token counts, cost breakdowns, and request metadata, enabling unauthorized use of connected AI provider accounts, billing fraud, and quota exhaustion.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 07/14/2026
This vulnerability represents a critical security flaw in the 9Router software version 0.4.41 that exposes sensitive authentication credentials through improper access control mechanisms. The issue stems from a missing authentication middleware implementation within the Next.js API routing framework, specifically affecting the /api/usage/stats endpoint which serves as an unauthorized entry point for retrieving confidential information. The flaw allows remote attackers to execute a single unauthenticated request that returns complete plaintext API keys along with associated metadata including token usage statistics, cost calculations, and request details. This represents a severe violation of security principles where sensitive data that should be protected through proper authentication mechanisms is made accessible without any authorization checks.
The technical implementation of this vulnerability demonstrates a fundamental failure in the application's security architecture where the development team neglected to implement appropriate middleware controls for protecting sensitive API endpoints. The Next.js framework typically enforces strict routing and middleware patterns that should automatically validate authentication tokens before allowing access to protected resources, yet this implementation bypasses those safeguards entirely. Attackers can exploit this by simply sending a GET request to the specific endpoint without providing any credentials, causing the system to return comprehensive information about all connected AI provider accounts including their full API key strings. This exposure creates multiple attack vectors since the retrieved keys can be immediately used to access external services, potentially leading to unauthorized transactions and resource consumption.
The operational impact of this vulnerability extends far beyond simple information disclosure, creating significant financial and security risks for affected organizations. The ability to obtain plaintext API keys enables attackers to consume billing resources from connected AI provider accounts, potentially leading to substantial financial losses through unauthorized usage charges. Additionally, the exposure of complete credential sets allows for full account compromise where attackers can make additional requests to external services using the stolen keys, potentially exhausting service quotas and causing denial of service conditions for legitimate users. The inclusion of cost breakdowns and token counts in the response data provides attackers with detailed information about service usage patterns, enabling them to optimize their attack strategies and maximize financial gain.
Organizations should immediately implement authentication middleware controls to protect all API endpoints that handle sensitive data, particularly those related to external service integrations and billing information. The recommended mitigation involves adding proper authentication checks using Next.js middleware functions that validate incoming requests against established security tokens or session identifiers before processing any sensitive data retrieval operations. Security teams must also conduct comprehensive audits of all API endpoints to identify similar authentication gaps and implement least privilege access controls for all data exposure points. This vulnerability aligns with CWE-306: "Missing Authentication for Critical Function" and represents a clear violation of ATT&CK technique T1566.002: "Phishing for Information" through the exploitation of unauthenticated API endpoints, requiring immediate remediation to prevent unauthorized access to sensitive organizational data and financial resources.
The incident highlights the critical importance of implementing robust security controls during application development phases, particularly when dealing with third-party service integrations that involve sensitive credential management. Organizations should establish mandatory security review processes for all API endpoint implementations, ensuring that proper authentication mechanisms are in place before deployment. Regular penetration testing and security scanning should be conducted to identify similar vulnerabilities across the entire application architecture, while automated monitoring systems should be deployed to detect unauthorized access attempts to sensitive data endpoints. The exploitation of this vulnerability demonstrates how seemingly minor implementation oversights can create significant security risks, emphasizing the need for comprehensive security training and adherence to secure coding practices throughout the development lifecycle.