# CVE-2026-13534: CherryHQ cherry-studio CherryIN Preload API MemoryService.ts sha256 authorization

> Remote attackers can bypass authorization in Cherry Studio's memory service via argument manipulation, though exploitability is difficult and the feature is slated for removal.

- **Severity:** Low 2.3 (`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:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-qwwm-4xhq-q4m4

## What is CVE-2026-13534?

CVE-2026-13534 is a low-severity authentication bypass vulnerability in CherryHQ cherry-studio, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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."

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-13534?


## How do I fix CVE-2026-13534?

No fix has been published for CVE-2026-13534 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13534 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13534 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13534 and fix it if it is affected.

What it is: CVE-2026-13534 is a low-severity authentication bypass vulnerability in CherryHQ cherry-studio, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13534 exists.

Affected product: CherryHQ cherry-studio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13534/ (Markdown: https://insights.sbomify.com/CVE-2026-13534/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13534
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13534
- OSV: https://osv.dev/vulnerability/CVE-2026-13534

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13534/
Summaries are generated and may contain mistakes; the official description above is the record.