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

> A local attacker can exploit improper privilege handling in the Open File Dialog to execute actions with administrator-level privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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:** 27 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-3w44-vqrj-hgrj

## What is CVE-2025-69689?

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

### Official description

The Fan Control application V251 contains an improper privilege handling vulnerability in its Open File Dialog. The dialog processes user-supplied paths with elevated permissions, which can be exploited by a local attacker to perform actions with administrator-level privileges.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2025-69689 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69689 is a high-severity vulnerability in n/a, published on 27 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-69689 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-69689/ (Markdown: https://insights.sbomify.com/CVE-2025-69689/index.md)
```

## Sources

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

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