Loading vulnerability…
CVE-2025-50505 affects Clash Verge Rev through 2.2.3 and is fixed in 2.3.0. The application installs the privileged system service clash-verge-service by default and exposes sensitive functionality through an unauthorized local HTTP API endpoint, /start_clash. A local user can invoke this endpoint and supply an arbitrary bin_path parameter, which is passed directly to the service process for execution. Because the service runs with elevated privileges, this design allows an unprivileged local user to cause execution of attacker-controlled binaries in a privileged context, resulting in local privilege escalation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.