Code Injection in Cherry Ai (CVE-2025-61929)
Summary
Code injection in Cherry Ai (CVE-2025-61929). Successful exploitation can lead to full system takeover. Exploitable via handleMcpProtocolUrl.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-61929 has been found in Cherry Ai.
Attackers can target a specific entry point like handleMcpProtocolUrl over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Cherry Ai CVE-2025-61929" on the vendor's site.
CVE-2025-61929 (Cherry Ai) — CWE-94 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: handleMcpProtocolUrl
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in Cherry Ai. Attackers reach the vulnerable code path via handleMcpProtocolUrl without authentication.
Check the vendor advisory for the affected versions of Cherry Ai. Attack surface: handleMcpProtocolUrl.
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Cherry Ai を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com