CVE-2025-54382: CherryHQ cherry-studio · OS Command Injection
Affects CherryHQ cherry-studioSource CVE Database V5
Not known to be exploited · CVSS 9.7 Critical · fixed in 1.5.2 : patch CherryHQ cherry-studio as a priority.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 7.4% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CherryHQ cherry-studio | Affected
| Fixed in– |
AI-suggested
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.
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.