Skip to main content
VulnerabilityPublished

CVE-2025-54063: CherryHQ cherry-studio · Code Injection

Affects CherryHQ cherry-studioSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High · fixed in 1.5.1 : patch CherryHQ cherry-studio soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.5.1
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

AI-suggested

  1. Immediate upgrade: Organizations should promptly update Cherry Studio to version 1.5.1 or later, where the vulnerability is patched.
  2. URL handling restrictions: Implement endpoint security policies that restrict or monitor the invocation of custom URL handlers, especially those linked to Cherry Studio, to prevent automatic or unintended execution.
  3. User awareness training: Educate users about the risks of clicking unknown or suspicious links, particularly those that could trigger application-specific handlers.
  4. Network segmentation: Limit the exposure of endpoints running Cherry Studio by segmenting networks and applying strict access controls to reduce the attack surface.
  5. Endpoint detection and response (EDR): Deploy and tune EDR solutions to detect anomalous behaviors indicative of code injection or remote code execution attempts.
  6. Application whitelisting: Use application control mechanisms to prevent unauthorized code execution or the launching of unexpected processes triggered by URL handlers.
  7. Monitor for Indicators of Compromise (IoCs): Although no exploits are known in the wild, monitor logs and network traffic for suspicious URL handler invocations or unusual process executions related to Cherry Studio.
  8. Incident response readiness: Prepare and test incident response plans to quickly contain and remediate any exploitation attempts.

Description

Cherry Studio is a desktop client that supports for multiple LLM providers. From versions 1.4.8 to 1.5.0, there is a one-click remote code execution vulnerability through the custom URL handling. An attacker can exploit this by hosting a malicious website or embedding a specially crafted URL on any website. If a victim clicks the exploit link in their browser, the app’s custom URL handler is triggered, leading to remote code execution on the victim’s machine. This issue has been patched in version 1.5.1.

References

Community reviews

Loading reviews…