Cherry Studio versions 1.2.2 through 1.9.12, fixed in commit 1518530, contain a remote code execution vulnerability in SearchService that allows remote attackers to execute arbitrary code by delivering malicious JavaScript through controlled search provider content loaded into an Electron BrowserWindow configured with nodeIntegration enabled and contextIsolation disabled. Attackers who control a search engine provider, individual search result pages, or provider settings pages can execute JavaScript with full Node.js privileges, gaining access to fs, child_process, os, and process.env under the operating-system account of the Cherry Studio process.
CVE-2026-40501
This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026Cherry Studio RCE via SearchService nodeIntegration Misconfiguration | Advisories | VulnCheck
https://www.vulncheck.com/advisories/cherry-studio-rce-via-searchservice-nodeintegration-misconfigurationcommit 151853035e8e (CherryHQ/cherry-studio)
Fix landed in CherryHQ/cherry-studio commit 151853035e8e — awaiting tagged release
https://github.com/CherryHQ/cherry-studio/commit/151853035e8e417a51559ebfc243eda98361a882Cherry Studio SearchService RCE via Node.js Integration (GHSA-jhw3-9q9r-gc5w) · GitHub
https://gist.github.com/Mundi-Xu/99af1b08275fd437cfb79bfe481e68b7Vendor Advisories for CVE-2026-40501(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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.
- 2026-07-15 17:54 UTCEG score recompute
- 2026-07-15 17:53 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-40501?
When was CVE-2026-40501 disclosed?
What is the CVSS score of CVE-2026-40501?
How do I remediate CVE-2026-40501?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-40501
Is Your Infrastructure Affected by CVE-2026-40501?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.