Clash Project maintains a proxy and network utility focused on traffic routing and tunneling, with a vulnerability profile centered on access-control and input-handling weaknesses. The recurring exposure includes improper file/directory permissions, cross-site scripting in web interfaces, permission misconfiguration, and origin validation errors—patterns typical of configuration-driven network tools where authentication boundaries and request validation are critical. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Clash Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-26255CRITICAL Clash for Windows v0.19.8 was discovered to allow arbitrary code execution via a crafted payload injected into the Proxies name column. | Mar 28, 2022 | 9.8 | 31 | NO | NO |
CVE-2023-24205CRITICAL Clash for Windows v0.20.12 was discovered to contain a remote code execution (RCE) vulnerability which is exploited via overwriting the configuration file (cfw-setting.yaml). | Feb 23, 2023 | 9.8 | 30 | NO | NO |
CVE-2020-24772HIGH In Dreamacro Clash for Windows v0.11.4, an attacker could embed a malicious iframe in a website with a crafted URL that would launch the Clash Windows client and force it to open a | Mar 21, 2022 | 8.8 | 28 | NO | NO |
CVE-2022-40126HIGH A misconfiguration in the Service Mode profile directory of Clash for Windows v0.19.9 allows attackers to escalate privileges and execute arbitrary commands when Service Mode is ac | Sep 29, 2022 | 7.8 | 26 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Clash Project.
Media articles that mention a CVE ID that affects a product developed by Clash Project — matched by CVE ID, not by vendor name.