dbcve.org
Cherry StudioApplication · Cherry Ai

CVE-2025-54074

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 1.5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cherry Studio is a desktop client that supports for multiple LLM providers. From versions 1.2.5 to 1.5.1, Cherry Studio is vulnerable to OS Command Injection during a connection with a malicious MCP server in HTTP Streamable mode. Attackers can setup a malicious MCP server with compatible OAuth authorization server endpoints and trick victims into connecting it, leading to OS command injection in vulnerable clients. This issue has been patched in version 1.5.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cherry Studio versions 1.2.5 through 1.5.1 contain an OS command injection vulnerability in the MCP server client connection logic when using HTTP Streamable mode. Attackers can deploy a malicious MCP server with crafted OAuth authorization endpoints to trigger arbitrary OS command execution on victims who connect to it.

MitigationUpgrade Cherry Studio to version 1.5.2 or later. Until upgraded, avoid connecting to any untrusted or unknown MCP servers, as attackers could use malicious OAuth endpoints to inject and execute operating system commands.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cherry StudioApplication
Affected:>= 1.2.5, < 1.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Cherry Studio installed version
    Check the application's version number (typically found in the app's About section, settings, or the executable metadata). Compare this version against the affected range: 1.2.5 through 1.5.1.
    Affected if The installed version is 1.2.5, 1.2.6, 1.2.7, 1.2.8, 1.2.9, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.5.0, or 1.5.1.
  2. Identify configured MCP server connections
    Locate the MCP server configuration or list of connected servers within the Cherry Studio application (typically in settings or server management areas).
    Affected if Any MCP servers are configured or connected, especially if they are from untrusted or unknown sources.
  3. Verify if HTTP Streamable mode is enabled
    Check the connection settings or configuration for MCP server connections to see if HTTP Streamable mode is the selected transport method.
    Affected if HTTP Streamable mode is enabled for any MCP server connection.
  4. Inspect OAuth endpoint configurations
    Review the OAuth authorization endpoint URLs configured for any MCP servers. Look for non-standard or suspicious URLs that could be attacker-controlled.
    Affected if Any MCP server is configured with an OAuth authorization endpoint from an untrusted or unfamiliar domain.

You are affected if your Cherry Studio version is 1.2.5 through 1.5.1 and you have any MCP servers configured with HTTP Streamable mode enabled, particularly if connecting to untrusted servers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.2 or later
Fixed in 1.5.2
Vendor patch github.com →
Interim mitigation

Upgrade Cherry Studio to version 1.5.2 or later. Until upgraded, avoid connecting to any untrusted or unknown MCP servers, as attackers could use malicious OAuth endpoints to inject and execute operating system commands.

Recommended fix High confidence

1.5.2

  1. Check current Cherry Studio version by navigating to Help > About in the application menu
  2. If the installed version is between 1.2.5 and 1.5.1 (inclusive), the application is vulnerable
  3. Download Cherry Studio version 1.5.2 or later from the official GitHub releases page (https://github.com/CherryHQ/cherry-studio/releases)
  4. Install the updated version, ensuring to replace the existing installation
  5. Verify the upgrade was successful by checking the version again in Help > About

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cherry Studio Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54074 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data