Skip to content
Applications

CVE-2026-40501

8.6
High
EPSS 0.80%Patch availableJul 16, 2026

RCE in Cherry Studio via malicious search-provider JavaScript in Electron window.

common questions

Is CVE-2026-40501 being exploited?

Not confirmed. CVE-2026-40501 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.80% probability of exploitation in the next 30 days.

How severe is CVE-2026-40501?

CVE-2026-40501 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-40501?

Yes. A fix has been recorded for CVE-2026-40501. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-40501 affect?

CVE-2026-40501 affects Cherry Studio 1.2.2–1.9.12, Electron apps with nodeIntegration enabled & contextIsolation disabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-40501?

Upgrade past 1.9.12 or apply commit 1518530; disable nodeIntegration and enable contextIsolation.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Cherry Studio 1.2.2–1.9.12Electron apps with nodeIntegration enabled & contextIsolation disabled
impact

Remote code execution: attacker-controlled search content runs Node.js with full fs/child_process access as app user.

action required

Immediate action required

affected versions
CherryHQ cherry-studio
  • affected>= 1.2.2 and <= 1.9.12
  • affected>= f9c6bddae5b91cc50872c76e791105fa219d0d34 and <= 151853035e8e417a51559ebfc243eda98361a882

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free