CVE-2026-40501: Cherry Studio RCE Vulnerability

CVE-2026-40501 Overview

Cherry Studio versions 1.2.2 through 1.9.12 contain a remote code execution vulnerability in the SearchService component. The flaw arises from an Electron BrowserWindow configured with nodeIntegration enabled and contextIsolation disabled. Attackers who control a search engine provider, search result page, or provider settings page can deliver malicious JavaScript that executes with full Node.js privileges. Successful exploitation grants access to fs, child_process, os, and process.env under the operating-system account running Cherry Studio. The issue is tracked under [CWE-829: Inclusion of Functionality from Untrusted Control Sphere]. The fix landed in commit 1518530.

Critical Impact
Attacker-controlled search content executes arbitrary Node.js code on the victim host, enabling file access, command execution, and environment variable theft.

Affected Products

Cherry Studio 1.2.2 through 1.9.12
Electron BrowserWindow instances with nodeIntegration: true and contextIsolation: false
Fixed in Cherry Studio commit 151853035e8e417a51559ebfc243eda98361a882

Discovery Timeline

2026-07-15 - CVE-2026-40501 published to NVD
2026-07-15 - Last updated in NVD database

Technical Details for CVE-2026-40501

Vulnerability Analysis

Cherry Studio's SearchService loads third-party search provider content into an Electron BrowserWindow. That window is instantiated with nodeIntegration: true and contextIsolation: false, which exposes the Node.js runtime directly to any JavaScript rendered inside it. Any script delivered through the search provider, individual result pages, or provider settings pages can therefore call Node built-ins such as require('child_process').exec() without a sandbox boundary.

The result is a full remote code execution primitive: attacker-controlled JavaScript inherits the privileges of the desktop process, reads and writes arbitrary files via fs, spawns processes via child_process, and exfiltrates secrets from process.env. Because Cherry Studio is an AI workstation, process.env frequently stores API keys for language model providers, making credential theft a first-order impact.

Root Cause

The root cause is an insecure Electron window configuration combined with loading untrusted remote content. Electron's security documentation explicitly warns against enabling nodeIntegration for windows that render remote or third-party content. The SearchService violated both principles by routing provider-controlled HTML into a Node-integrated renderer.

Attack Vector

Exploitation requires an attacker to control content served through a Cherry Studio search provider. This includes operating a malicious provider, compromising an upstream result page, or supplying a crafted provider settings page. User interaction is required, as noted by the UI:A metric, in the form of triggering a search that loads the malicious content.

typescript

// Security patch excerpt - refactor(ipc): remove dead legacy IPC channels and SearchService
// File: src/main/core/application/Application.ts
 private registerApplicationIpc(): void {
-    ipcMain.handle(IpcChannel.Application_Quit, () => this.quit())
-
     ipcMain.handle(IpcChannel.Application_Relaunch, (_, options?: Electron.RelaunchOptions) => {
       this.relaunch(options)
     })
// Source: https://github.com/CherryHQ/cherry-studio/commit/151853035e8e417a51559ebfc243eda98361a882

The patch removes the SearchService and its associated IPC channels entirely, eliminating the untrusted content sink rather than attempting to sanitize provider input. See the VulnCheck advisory and the public proof of concept for exploitation specifics.

Detection Methods for CVE-2026-40501

Indicators of Compromise

Cherry Studio processes spawning unexpected child processes such as cmd.exe, powershell.exe, /bin/sh, or bash shortly after a search action.
Outbound network connections from the Cherry Studio process to domains matching configured or newly added search providers.
Modifications to Cherry Studio's provider settings file that add unknown search engine URLs.
Read access to sensitive files such as ~/.ssh/, .env, or credential stores by the Cherry Studio binary.

Detection Strategies

Monitor for nodeIntegration-enabled Electron processes making outbound HTTP requests to non-allowlisted search domains.
Alert on process lineage where Cherry Studio is the parent of shell interpreters or scripting hosts.
Inspect application configuration for modifications to search provider endpoints outside change-management windows.

Monitoring Recommendations

Enable command-line auditing on endpoints running Cherry Studio to capture child process arguments.
Log DNS queries from developer workstations and correlate against known search provider allowlists.
Track reads of environment-variable-bearing files and API token stores by desktop AI tools.

How to Mitigate CVE-2026-40501

Immediate Actions Required

Upgrade Cherry Studio to a build that includes commit 151853035e8e417a51559ebfc243eda98361a882 or later.
Inventory endpoints running Cherry Studio versions 1.2.2 through 1.9.12 and prioritize them for patching.
Rotate any API keys, tokens, or credentials stored in process.env or configuration files accessible to Cherry Studio.
Review configured search providers and remove any that were added by untrusted users or automation.

Patch Information

The vendor fix is available in the Cherry Studio security commit. The patch removes the vulnerable SearchService and its legacy IPC channels rather than reconfiguring the Electron window, eliminating the attack surface entirely. Deploy the updated release across all affected workstations.

Workarounds

If immediate patching is not possible, restrict Cherry Studio to a curated allowlist of trusted search providers through configuration policy.
Block outbound network access from Cherry Studio to arbitrary domains at the host firewall or egress proxy.
Run Cherry Studio under a least-privilege operating-system account that lacks access to sensitive credential stores.

bash

# Verify installed Cherry Studio version and patch status
cherry-studio --version
# Confirm the running build includes the SearchService removal commit
git -C /path/to/cherry-studio log --oneline | grep 1518530