Skip to main content

CVE-2025-54382: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in CherryHQ cherry-studio

Critical
VulnerabilityCVE-2025-54382cvecve-2025-54382cwe-78
Published: Wed Aug 13 2025 (08/13/2025, 13:31:13 UTC)
Source: CVE Database V5
Vendor/Project: CherryHQ
Product: cherry-studio

Description

Cherry Studio is a desktop client that supports for multiple LLM providers. In version 1.5.1, a remote code execution (RCE) vulnerability exists in the Cherry Studio platform when connecting to streamableHttp MCP servers. The issue arises from the server’s implicit trust in the oauth auth redirection endpoints and failure to properly sanitize the URL. This issue has been patched in version 1.5.2.

AI-Powered Analysis

AILast updated: 08/13/2025, 14:03:11 UTC

Technical Analysis

CVE-2025-54382 is a critical remote code execution (RCE) vulnerability identified in Cherry Studio, a desktop client application developed by CherryHQ that supports multiple large language model (LLM) providers. The vulnerability specifically affects version 1.5.1 of Cherry Studio. The root cause of the issue lies in improper input validation and sanitization of URLs used during OAuth authentication redirection when connecting to streamableHttp MCP servers. The server implicitly trusts the OAuth authentication redirection endpoints without adequately neutralizing special characters or command injection vectors in the URL. This improper neutralization corresponds to CWE-78, which involves OS command injection vulnerabilities. An attacker can exploit this flaw by crafting malicious URLs that, when processed by the vulnerable Cherry Studio client, lead to arbitrary command execution on the victim's machine. The vulnerability has a CVSS 3.1 base score of 9.7, indicating a critical severity level with network attack vector, low attack complexity, no privileges required, but user interaction needed, and impacts confidentiality, integrity, and availability with a scope change. The vulnerability was publicly disclosed on August 13, 2025, and patched in version 1.5.2 of Cherry Studio. No known exploits are currently reported in the wild, but the high severity and ease of exploitation make it a significant threat if left unpatched. The vulnerability's exploitation could allow attackers to execute arbitrary OS commands remotely, potentially leading to full system compromise, data theft, or disruption of services.

Potential Impact

For European organizations, the impact of CVE-2025-54382 could be substantial, especially for those relying on Cherry Studio for integration with LLM providers or streamableHttp MCP servers. The ability to execute arbitrary commands remotely can lead to unauthorized access to sensitive data, disruption of business-critical applications, and potential lateral movement within corporate networks. Given the criticality of the vulnerability and the fact that it requires only user interaction (such as clicking a malicious link or connecting to a compromised server), phishing campaigns or supply chain attacks could be effective vectors. Organizations in sectors such as finance, healthcare, government, and technology—where data confidentiality and system integrity are paramount—are at heightened risk. Additionally, the vulnerability could be leveraged to deploy ransomware or other malware, amplifying operational and financial damages. The cross-platform nature of desktop clients means that both Windows and potentially macOS or Linux users could be affected, broadening the scope of impact. The lack of known exploits in the wild currently provides a window for proactive mitigation, but the critical severity score underscores the urgency for patching and risk management.

Mitigation Recommendations

To mitigate CVE-2025-54382 effectively, European organizations should take the following specific actions beyond generic patching advice: 1) Immediate upgrade all Cherry Studio clients to version 1.5.2 or later, which contains the fix for this vulnerability. 2) Implement strict network controls to restrict access to streamableHttp MCP servers, especially from untrusted or external sources, to reduce exposure to malicious OAuth redirection endpoints. 3) Employ endpoint detection and response (EDR) solutions capable of monitoring and blocking suspicious command execution patterns that may indicate exploitation attempts. 4) Conduct user awareness training focused on the risks of interacting with untrusted URLs or OAuth authentication prompts, emphasizing cautious behavior with links received via email or messaging platforms. 5) Review and harden OAuth configurations and redirection URL validation policies within the organization's identity and access management (IAM) framework to prevent implicit trust exploitation. 6) Monitor logs and network traffic for unusual OAuth redirection activities or connections to unknown MCP servers. 7) Establish an incident response plan tailored to remote code execution scenarios to enable rapid containment and remediation if exploitation is detected. These targeted measures will help reduce the attack surface and improve detection and response capabilities.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-07-21T16:12:20.734Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 689c9784ad5a09ad00420caa

Added to database: 8/13/2025, 1:47:48 PM

Last enriched: 8/13/2025, 2:03:11 PM

Last updated: 8/13/2025, 5:09:17 PM

Views: 5

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats