CVE-2026-13534

MEDIUMPre-NVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory (severity: LOW) published 2026-06-29. A secondary CVSS source baseline 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
5.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.0Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

CVSS v3
5.0
EG Score
5.0MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity50% × 45%
The EG Score, 5.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 29, 2026

Last Modified

June 29, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
No fix on record yet. Sources: github_pr.
generic

GitHub - CherryHQ/cherry-studio: AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs · GitHub

https://github.com/CherryHQ/cherry-studio/
github_pr

fix: scope memory deduplication hashes

Upstream fix in progress (PR #15413 · CherryHQ/cherry-studio, state=open)

https://github.com/CherryHQ/cherry-studio/pull/15413
generic

[Bug]: Memory deduplication ignores user and assistant scope · Issue #15411 · CherryHQ/cherry-studio · GitHub

https://github.com/CherryHQ/cherry-studio/issues/15411

Vendor Advisories for CVE-2026-13534(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 175 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 18:23 UTCEG score recompute
  2. 2026-10-11 14:57 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-09-23 07:36 UTCEG score recompute
  20. 2026-09-23 07:36 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  21. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-09-18 07:03 UTCEG score recompute
  24. 2026-09-18 07:03 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  25. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 75 more
  1. 2026-09-14 00:54 UTCEG score recompute
  2. 2026-09-14 00:54 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  3. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-09-12 15:17 UTCEG score recompute
  5. 2026-09-12 15:17 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  6. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-09-06 14:47 UTCEG score recompute
  13. 2026-09-06 14:47 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  14. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-08-30 19:00 UTCEG score recompute
  21. 2026-08-30 19:00 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  22. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-08-27 22:49 UTCEG score recompute
  25. 2026-08-27 22:49 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  26. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  28. 2026-08-24 21:46 UTCEG score recompute
  29. 2026-08-24 21:46 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  30. 2026-08-23 13:25 UTCEG score recompute
  31. 2026-08-23 13:25 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  32. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  33. 2026-08-22 10:37 UTCEG score recompute
  34. 2026-08-22 10:37 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  35. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  36. 2026-08-21 08:16 UTCEG score recompute
  37. 2026-08-21 08:16 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  38. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  39. 2026-08-20 05:55 UTCEG score recompute
  40. 2026-08-20 05:55 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  41. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  42. 2026-08-18 23:22 UTCEG score recompute
  43. 2026-08-18 23:22 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  44. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  45. 2026-08-16 16:42 UTCEG score recompute
  46. 2026-08-16 16:42 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  47. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  48. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  49. 2026-08-15 14:16 UTCEG score recompute
  50. 2026-08-15 14:16 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  51. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  52. 2026-08-14 11:54 UTCEG score recompute
  53. 2026-08-14 11:54 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  54. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-08-13 09:34 UTCEG score recompute
  56. 2026-08-13 09:34 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  57. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  58. 2026-08-12 07:13 UTCEG score recompute
  59. 2026-08-12 07:13 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  60. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  61. 2026-08-11 04:51 UTCEG score recompute
  62. 2026-08-11 04:51 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  63. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  64. 2026-08-10 02:30 UTCEG score recompute
  65. 2026-08-10 02:30 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  66. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  67. 2026-08-09 00:10 UTCEG score recompute
  68. 2026-08-09 00:10 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  69. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  70. 2026-08-07 21:49 UTCEG score recompute
  71. 2026-08-07 21:49 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  72. 2026-08-06 19:28 UTCEG score recompute
  73. 2026-08-06 19:28 UTCGHSA enrichmentGHSA-qwwm-4xhq-q4m4 · GitHub severity LOW · GitHub CVSS 5.0
  74. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  75. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-13534?
CVE-2026-13534 is a medium-severity vulnerability; its CVE record was published on June 29, 2026. 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…
When was the CVE record for CVE-2026-13534 published?
The CVE record for CVE-2026-13534 was published on June 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 29, 2026; the record at its source may have been updated since.
Is CVE-2026-13534 actively exploited?
CVE-2026-13534 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13534?
CVE-2026-13534 has a CVSS base score of 5.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-13534?
No fix for CVE-2026-13534 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-13534 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13534

Explore →

Is Your Infrastructure Affected by CVE-2026-13534?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs