Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-57755: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in musistudio claude-code-router

0
High
VulnerabilityCVE-2025-57755cvecve-2025-57755cwe-200cwe-942
Published: Thu Aug 21 2025 (08/21/2025, 16:21:33 UTC)
Source: CVE Database V5
Vendor/Project: musistudio
Product: claude-code-router

Description

claude-code-router is a powerful tool to route Claude Code requests to different models and customize any request. Due to improper Cross-Origin Resource Sharing (CORS) configuration, there is a risk that user API Keys or equivalent credentials may be exposed to untrusted domains. Attackers could exploit this misconfiguration to steal credentials, abuse accounts, exhaust quotas, or access sensitive data. The issue has been patched in v1.0.34.

AI-Powered Analysis

AILast updated: 08/21/2025, 16:47:53 UTC

Technical Analysis

CVE-2025-57755 is a high-severity vulnerability affecting musistudio's claude-code-router, a tool designed to route Claude Code requests to various models and customize these requests. The vulnerability arises from improper Cross-Origin Resource Sharing (CORS) configuration, which allows unauthorized domains to access sensitive information such as user API keys or equivalent credentials. CORS is a security feature implemented by browsers to restrict web page scripts from making requests to a different domain than the one that served the web page. If misconfigured, it can inadvertently expose sensitive data to malicious websites. In this case, the misconfiguration enables attackers to exploit the vulnerability by crafting malicious web pages that can steal API keys from legitimate users. These stolen credentials can then be used to abuse the affected accounts, potentially exhausting usage quotas or accessing sensitive data that the API keys protect. The vulnerability affects all versions of claude-code-router prior to version 1.0.34, where the issue has been patched. The CVSS 4.0 score of 8.1 reflects the high impact of this vulnerability, with no authentication or user interaction required for exploitation, and the attack vector being network-based. The vulnerability impacts confidentiality, integrity, and availability, as attackers can gain unauthorized access to sensitive credentials and misuse them. Although no known exploits are reported in the wild yet, the nature of the vulnerability makes it a significant risk if left unpatched.

Potential Impact

For European organizations using musistudio's claude-code-router, this vulnerability poses a serious risk. Exposure of API keys can lead to unauthorized access to internal systems or cloud services, resulting in data breaches, service disruptions, and financial losses due to quota exhaustion or fraudulent usage. Organizations relying on claude-code-router for routing AI model requests may face operational interruptions if attackers abuse stolen credentials. Additionally, sensitive data processed or accessed via these APIs could be compromised, violating data protection regulations such as GDPR. The reputational damage and potential regulatory penalties could be substantial. Since the vulnerability requires no user interaction or authentication, attackers can exploit it remotely and at scale, increasing the threat level. The absence of known exploits in the wild currently provides a window for mitigation, but the risk remains high due to the ease of exploitation and the sensitivity of exposed information.

Mitigation Recommendations

European organizations should immediately upgrade claude-code-router to version 1.0.34 or later, where the CORS misconfiguration has been corrected. Beyond patching, organizations should audit their CORS policies to ensure they follow the principle of least privilege, allowing only trusted domains to access resources. Implement strict validation of the Origin header and avoid using wildcard ('*') in Access-Control-Allow-Origin headers. Additionally, rotate any API keys or credentials that may have been exposed prior to patching to prevent unauthorized access. Employ monitoring and anomaly detection on API usage to identify unusual patterns indicative of credential abuse. Network-level controls such as Web Application Firewalls (WAFs) can be configured to block suspicious cross-origin requests. Finally, educate developers and security teams on secure CORS configuration and regularly review third-party components for vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-08-19T15:16:22.916Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68a74a30ad5a09ad00128c41

Added to database: 8/21/2025, 4:32:48 PM

Last enriched: 8/21/2025, 4:47:53 PM

Last updated: 1/7/2026, 6:12:07 AM

Views: 95

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats