CVE-2026-40501

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

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.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
35.7%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

Cherry Studio RCE via SearchService nodeIntegration Misconfiguration | Advisories | VulnCheck

https://www.vulncheck.com/advisories/cherry-studio-rce-via-searchservice-nodeintegration-misconfiguration
github_commit

commit 151853035e8e (CherryHQ/cherry-studio)

Fix landed in CherryHQ/cherry-studio commit 151853035e8e — awaiting tagged release

https://github.com/CherryHQ/cherry-studio/commit/151853035e8e417a51559ebfc243eda98361a882
generic🟡 PoC Available

Cherry Studio SearchService RCE via Node.js Integration (GHSA-jhw3-9q9r-gc5w) · GitHub

https://gist.github.com/Mundi-Xu/99af1b08275fd437cfb79bfe481e68b7

Vendor 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 9× in last 7d / 12× 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-23 03:11 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 18:39 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 06:17 UTCGHSA enrichment
  11. 2026-07-15 17:54 UTCEG score recompute
  12. 2026-07-15 17:53 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-40501?
CVE-2026-40501 is a high vulnerability published on July 15, 2026. 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…
When was CVE-2026-40501 disclosed?
CVE-2026-40501 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40501 actively exploited?
CVE-2026-40501 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40501?
CVE-2026-40501 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-40501?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40501, 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-40501

Explore →

Is Your Infrastructure Affected by CVE-2026-40501?

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

Start Free Scan →Browse All CVEs