Is there a public PoC exploit available for CVE-2026-13534?

Yes, a public proof-of-concept exploit is available for CVE-2026-13534. Prioritise patching immediately. EPSS: 0.2%.

Is there a patch available for CVE-2026-13534?

Yes, a patch is available for CVE-2026-13534. Update the affected software to the latest version immediately.

Cherry Studio CVE-2026-13534

Q: What is the CVSS score of CVE-2026-13534?

CVE-2026-13534 has a CVSS 4.0 base score of 1.3 (Low). CVSS vector: 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-40031 LOW

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-06-29 VulDB

GHSA-qwwm-4xhq-q4m4

Authentication Bypass Cherry Studio Cherryhq

1.3

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

1.3 LOW

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

4.2 MEDIUM

Network-reachable API delivery (AV:N), requires crafting a hash-colliding payload (AC:H), valid authenticated session needed (PR:L); no scope change or availability impact observed.

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

4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

Jun 29, 2026 - 06:22 NVD

2.3 (LOW) 1.3 (LOW)

Source Code Evidence Fetched

Jun 29, 2026 - 05:46 vuln.today

Analysis Generated

Jun 29, 2026 - 05:46 vuln.today

DescriptionCVE.org

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

AnalysisAI

Authorization bypass in CherryHQ Cherry Studio up to version 1.9.7 allows authenticated remote attackers to cross user/agent memory isolation boundaries by manipulating memory content to produce SHA-256 hash collisions in the MemoryService deduplication logic. The vulnerable CherryIN Preload API component computed memory hashes solely from content, without scoping them to userId or agentId, enabling crafted inputs to match records belonging to other users. A public exploit exists per GitHub issue #15411, and a vendor patch is available via PR #15413; the vendor notes the memory feature is slated for removal in v2.

Technical ContextAI

Cherry Studio is an Electron-based AI desktop client. The affected component is MemoryService.ts within the application's main process, exposed via the CherryIN Preload API. The deduplication logic originally computed the SHA-256 hash over only the trimmed memory string (crypto.createHash('sha256').update(trimmedMemory).digest('hex')), with no binding to the authenticated user's userId or agentId. This is a textbook CWE-639 (Authorization Bypass Through User-Controlled Key) flaw: the key used to look up and gate records is derived from user-controlled data without incorporating an authoritative, non-forgeable user scope. The PR diff at https://github.com/CherryHQ/cherry-studio/pull/15413 confirms the fix adds userId, agentId, and a schema version constant to the hashed payload, making each hash cryptographically scoped to its owner. CPE coverage is broad: cpe:2.3:a:cherryhq:cherry-studio:*:*:*:*:*:*:*:* covering all versions through 1.9.7.

RemediationAI

A patch is available as GitHub Pull Request #15413 (https://github.com/CherryHQ/cherry-studio/pull/15413), which scopes the SHA-256 deduplication hash to incorporate userId, agentId, and a schema version constant. Users should upgrade to a Cherry Studio release that incorporates this fix; no exact patched release version is independently confirmed from available data - verify the fix is present in the installed version before considering the system remediated. As a compensating control when immediate upgrade is not feasible, disabling the memory feature entirely within Cherry Studio's settings eliminates the vulnerable code path; the trade-off is loss of memory-assisted conversational context. The vendor has publicly stated that the memory feature is planned for removal in v2, so the long-term surface is inherently bounded.