EUVD-2026-44747
GHSA-5c46-rj6r-wvm8
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-delivered via untrusted search content with no auth (PR:N) but requires the victim to interact with it (UI:R); full host-account compromise gives C/I/A:H.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
3DescriptionCVE.org
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.
Articles & Coverage 1
AnalysisAI
Remote code execution in Cherry Studio 1.2.2 through 1.9.12 lets attackers who control search-provider content run arbitrary Node.js code because the SearchService loads that content into an Electron BrowserWindow with nodeIntegration enabled and contextIsolation disabled. An attacker controlling a search engine provider, search result page, or provider settings page can execute JavaScript with full Node.js privileges under the OS account running the app. Publicly available exploit code exists (VulnCheck/Mundi-Xu gist) and a vendor patch (commit 1518530) is available; the flaw is not currently listed in CISA KEV.
Technical ContextAI
Cherry Studio is an Electron-based desktop AI client (cpe:2.3:a:cherryhq:cherry-studio). Electron renders web content in Chromium BrowserWindows; when a window is created with nodeIntegration:true and contextIsolation:false, JavaScript running in that renderer has direct access to Node.js primitives (require, process, module) with no security boundary between untrusted page content and the main-process runtime. This maps to CWE-829 (Inclusion of Functionality from an Untrusted Control Sphere): the SearchService pulls externally controlled provider/result/settings content into a privileged execution context. Any script in that page can therefore reach fs, child_process, os, and process.env, enabling file read/write, command execution, and secret exfiltration under the Cherry Studio process account.
RemediationAI
Upgrade to a Cherry Studio build that includes the fix commit 151853035e8e417a51559ebfc243eda98361a882 (Upstream fix available via commit; the patched release tag is not independently confirmed from the provided data, so verify the exact released version against the vendor's release notes before deploying). The root cause is an insecure Electron BrowserWindow configuration, so the durable fix is to load search-provider content with nodeIntegration disabled and contextIsolation enabled behind a preload bridge. Until patched, restrict exposure by not adding or using untrusted custom search engine providers, avoiding attacker-supplied provider/settings URLs, and treating the built-in web search feature as untrusted; note the trade-off that disabling or limiting the search feature reduces functionality. Consult the VulnCheck advisory (https://www.vulncheck.com/advisories/cherry-studio-rce-via-searchservice-nodeintegration-misconfiguration) for details.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Share
External POC / Exploit Code
Leaving vuln.today