CVE-2026-13534: CherryHQ cherry-studio · Authorization Bypass
Affects CherryHQ cherry-studioSource CVE Database V5
Public exploit available · CVSS 2.3 Low.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 29 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CherryHQcherry-studio | Affected
| Fixed in– |
GitHubcherryhq/cherry-studiopkg:github/cherryhq/cherry-studioOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:cherryhq:cherry-studio:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor plans to remove the affected memory component in version 2.0, which will mitigate this issue. Until then, users should consider the risk low but remain cautious. Monitor vendor communications for updates or patches. No immediate action is mandated by the vendor.
Description
A vulnerability was detected in CherryHQ cherry-studio up to 1.9.7. This affects the function sha256 of the file src/main/services/memory/MemoryService.ts of the component CherryIN Preload API. Performing a manipulation of the argument state results in authorization bypass. The attack can be initiated remotely. The attack's complexity is rated as high. It is indicated that the exploitability is difficult. The exploit is now public and may be used. The vendor explains, that "[m]emory is planned to be removed in v2 version."
References
- vuldb.com/vuln/374542 (opens in a new tab)
- vuldb.com/vuln/374542/cti (opens in a new tab)
- vuldb.com/cve/CVE-2026-13534 (opens in a new tab)
- vuldb.com/submit/841998 (opens in a new tab)
- github.com/CherryHQ/cherry-studio/issues/15411 (opens in a new tab)
- github.com/CherryHQ/cherry-studio/pull/15413 (opens in a new tab)
- github.com/CherryHQ/cherry-studio/ (opens in a new tab)