Quick answers
- Is CVE-2026-13534 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13534 being exploited in the wild.
- How severe is CVE-2026-13534?
- Medium severity, with a CVSS score of 5, published 29 June 2026.
- Which products and versions are affected?
- CherryHQ Cherry Studio up to 1.9.7.
- Is there a fix for CVE-2026-13534?
- A patch was published on 2026-05-29: Pull request 15413 submitted to address the hashing scope issue. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13534 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-13534?
- Check whether you run CherryHQ Cherry Studio at an affected version. 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.7) exists within the `sha256` function of `MemoryService.ts` in the CherryIN Preload API. The root cause is that memory deduplication used a global SHA-256 hash of the memory text without incorporating user or assistant identifiers. This allows a remote attacker with low privileges to manipulate the 'state' argument, leading to an authorization bypass where one user's data can collide with or block another's. A pull request (#15413) has been proposed to scope these hashes by including the user_id and agent_id, though the vendor has indicated this component may be removed entirely in version 2.0.
Affected products
- CherryHQ cherry-studio up to 1.9.7
Timeline
- 2026-05-29: patched: Pull request 15413 submitted to address the hashing scope issue.
- 2026-06-29: advisory: CVE-2026-13534 published.