CVE-2026-13524

MEDIUMPre-NVD 5.65.6—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.6Exploit: NoneExposed: 0

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

A security vulnerability has been detected in CherryHQ cherry-studio up to 1.9.6. This vulnerability affects unknown code of the file src/main/services/mcp/oauth/callback.ts of the component MCP OAuth Local Callback Server. The manipulation of the argument code leads to improper authorization. The attack can be initiated remotely. The attack is considered to have high complexity. It is stated that the exploitability is difficult. The exploit has been disclosed publicly and may be used. The pull request to fix this issue awaits acceptance.

CVSS v3
5.6
EG Score
5.6(high)
EPSS
17.8%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
No patch confirmed yet. Sources: github_pr.
github_pr

fix: validate MCP OAuth callback state

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

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

[Bug]: MCP OAuth callback accepts first code without state validation · Issue #15372 · CherryHQ/cherry-studio · GitHub

https://github.com/CherryHQ/cherry-studio/issues/15372
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/

Vendor Advisories for CVE-2026-13524(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 22× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:11 UTCEG score recompute
  3. 2026-07-06 16:11 UTCGHSA enrichment
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 14:13 UTCEG score recompute
  6. 2026-07-05 14:13 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 12:15 UTCEG score recompute
  10. 2026-07-04 12:15 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 10:16 UTCEG score recompute
  13. 2026-07-03 10:16 UTCGHSA enrichment
  14. 2026-07-02 08:17 UTCEG score recompute
  15. 2026-07-02 08:17 UTCGHSA enrichment
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-07-01 06:19 UTCEG score recompute
  19. 2026-07-01 06:19 UTCGHSA enrichment
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 04:21 UTCEG score recompute
  22. 2026-06-30 04:21 UTCGHSA enrichment
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 04:03 UTCNVD updateCVSS v4 → 2.9
  25. 2026-06-29 02:23 UTCEG score recompute
Show 1 more
  1. 2026-06-29 02:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-13524?
CVE-2026-13524 is a medium vulnerability published on June 29, 2026. A security vulnerability has been detected in CherryHQ cherry-studio up to 1.9.6. This vulnerability affects unknown code of the file src/main/services/mcp/oauth/callback.ts of the component MCP OAuth Local Callback Server. The manipulation of the argument code leads to improper authorization. The…
When was CVE-2026-13524 disclosed?
CVE-2026-13524 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13524 actively exploited?
CVE-2026-13524 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13524?
CVE-2026-13524 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2026-13524?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13524, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-13524?

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

Start Free Scan →Browse All CVEs