Is CVE-2026-13524 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-13524 being exploited in the wild.

How severe is CVE-2026-13524?

Medium severity, with a CVSS score of 5.6, published 29 June 2026.

Which products and versions are affected?

CherryHQ cherry-studio up to 1.9.6.

Is there a fix for CVE-2026-13524?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-13524 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-13524?

Check whether you run CherryHQ Cherry Studio. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-13524: CherryHQ cherry-studio improper authorization in MCP OAuth callback

CVE-2026-13524 · Severity: medium · CVSS 5.6 · Published 2026-06-29

Cherry Studio, an AI productivity application, contains a security flaw in how it handles login and authorization for third-party services (MCP OAuth). An attacker could potentially trick the application into linking to a malicious account or intercepting the connection process if they can send a request to the user's computer while a login is in progress. This could lead to a situation where the user's AI tools are connected to an attacker-controlled service, potentially exposing sensitive prompts or data.

Technologies: CherryHQ Cherry Studio. Vendors: CherryHQ.

Quick answers

Is CVE-2026-13524 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-13524 being exploited in the wild.
How severe is CVE-2026-13524?: Medium severity, with a CVSS score of 5.6, published 29 June 2026.
Which products and versions are affected?: CherryHQ cherry-studio up to 1.9.6.
Is there a fix for CVE-2026-13524?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-13524 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-13524?: Check whether you run CherryHQ Cherry Studio. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in CherryHQ cherry-studio up to version 1.9.6 exists within the MCP OAuth Local Callback Server component (src/main/services/mcp/oauth/callback.ts). The implementation fails to validate the 'state' parameter during the OAuth callback flow and uses a non-strict path prefix check (startsWith) for the callback URL. A remote attacker can exploit this by winning a race condition during a pending OAuth transaction, submitting a malicious authorization code to the local loopback server. This results in OAuth callback injection or login CSRF, potentially leading to authorization binding confusion or sensitive data exposure depending on the specific MCP service capabilities. A fix involving per-flow state generation and exact path matching has been proposed in pull request #15388.

Affected products

CherryHQ cherry-studio up to 1.9.6

Timeline

2026-05-28: disclosed: Issue and fix PR submitted to GitHub repository
2026-06-29: advisory: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.