# CVE-2025-50505: Privilege escalation in n/a

> Local attackers can escalate privileges by exploiting an unauthorized HTTP API in Clash Verge Rev that executes arbitrary binaries via the system service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2025
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-225v-733h-9gwv

## What is CVE-2025-50505?

CVE-2025-50505 is a high-severity vulnerability in n/a, published on 7 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Clash Verge Rev thru 2.2.3 (fixed in 2.3.0) forces the installation of system services(clash-verge-service) by default and exposes key functions through the unauthorized HTTP API `/start_clash`, allowing local users to submit arbitrary bin_path parameters and pass them directly to the service process for execution, resulting in local privilege escalation.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2025-50505?


## How do I fix CVE-2025-50505?

No fix has been published for CVE-2025-50505 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-50505 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50505 exists.

Public exploit code:

- https://github.com/a0yami/CVE-2025-50505 (github_poc): https://github.com/a0yami/CVE-2025-50505

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50505 and fix it if it is affected.

What it is: CVE-2025-50505 is a high-severity vulnerability in n/a, published on 7 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50505 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-50505/ (Markdown: https://insights.sbomify.com/CVE-2025-50505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-50505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-50505
- OSV: https://osv.dev/vulnerability/CVE-2025-50505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-50505/
Summaries are generated and may contain mistakes; the official description above is the record.