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

> Local attackers can read sensitive daemon data to steal tokens and escalate privileges to root due to insecure default permissions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2025
- **Updated:** 22 Aug 2025
- **Also known as:** GHSA-wv45-cw2m-63r8

## What is CVE-2025-50691?

CVE-2025-50691 is a medium-severity vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MCSManager 10.5.3 daemon process runs as a root account by default, and its sensitive data (including tokens and terminal content) is stored in the data directory, readable by all users. Other users on the system can read the daemon's key and use it to log in, leading to privilege escalation.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-50691 being exploited?

There is no known exploitation of CVE-2025-50691 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50691 is a medium-severity vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50691 in the wild and no public exploit code.

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-50691/ (Markdown: https://insights.sbomify.com/CVE-2025-50691/index.md)
```

## Sources

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

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