# CVE-2025-61929: Cherry Studio allows one-click on a specific URL to cause a command to execute

> Cherry Studio allows remote code execution via a malicious custom protocol URL that triggers command execution upon user click.

- **Severity:** Critical 9.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Oct 2025
- **Updated:** 10 Oct 2025
- **Also known as:** GHSA-hh6w-rmjc-26f6

## What is CVE-2025-61929?

CVE-2025-61929 is a critical command injection vulnerability in CherryHQ cherry-studio, published on 10 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cherry Studio is a desktop client that supports for multiple LLM providers. Cherry Studio registers a custom protocol called `cherrystudio://`. When handling the MCP installation URL, it parses the base64-encoded configuration data and directly executes the command within it. In the files `src/main/services/ProtocolClient.ts` and `src/main/services/urlschema/mcp-install.ts`, when receiving a URL of the `cherrystudio://mcp` type, the `handleMcpProtocolUrl` function is called for processing. If an attacker crafts malicious content and posts it on a website or elsewhere (there are many exploitation methods, such as creating a malicious website with a button containing this malicious content), when the user clicks it, since the pop-up window contains normal content, the direct click is considered a scene action, and the malicious command is directly triggered, leading to the user being compromised. As of time of publication, no known patched versions exist.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-61929?

It affects 1 product.


Products: Cherry-Ai Cherry Studio.

## How do I fix CVE-2025-61929?

No fix has been published for CVE-2025-61929 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-61929 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61929 exists.

## Other vulnerabilities in CherryHQ cherry-studio

- [CVE-2025-54382](https://insights.sbomify.com/CVE-2025-54382/): Cherry Studio RCE Vulnerability Disclosure (critical 9.7)
- [CVE-2025-54063](https://insights.sbomify.com/CVE-2025-54063/): Cherry Studio One-click Remote Code Execution Vulnerability through Custom URL Handling (high 8.0)
- [CVE-2025-54074](https://insights.sbomify.com/CVE-2025-54074/): Cherry Studio is Vulnerable to OS Command Injection during Connection with a Malicious MCP Server (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61929 and fix it if it is affected.

What it is: CVE-2025-61929 is a critical command injection vulnerability in CherryHQ cherry-studio, published on 10 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61929 exists.

Affected product: CherryHQ cherry-studio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-61929/ (Markdown: https://insights.sbomify.com/CVE-2025-61929/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61929
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61929
- OSV: https://osv.dev/vulnerability/CVE-2025-61929

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-61929/
Summaries are generated and may contain mistakes; the official description above is the record.