# CVE-2025-15569: Artifex MuPDF win_main.c get_system_dpi uncontrolled search path

> Local attackers can exploit an uncontrolled search path in MuPDF on Windows to potentially execute arbitrary code.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X`)
- **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:** 10 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-8qc5-j3h9-pmjh, UBUNTU-CVE-2025-15569

## What is CVE-2025-15569?

CVE-2025-15569 is a high-severity path traversal vulnerability in Artifex MuPDF, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in Artifex MuPDF up to 1.26.1 on Windows. The impacted element is the function get_system_dpi of the file platform/x11/win_main.c. This manipulation causes uncontrolled search path. The attack requires local access. The attack is considered to have high complexity. The exploitability is regarded as difficult. Upgrading to version 1.26.2 is sufficient to resolve this issue. Patch name: ebb125334eb007d64e579204af3c264aadf2e244. Upgrading the affected component is recommended.

Weakness: CWE-427 (Uncontrolled Search Path Element), CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2025-15569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15569 is a high-severity path traversal vulnerability in Artifex MuPDF, published on 10 Feb 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-15569 in the wild and no public exploit code.

Affected product: Artifex MuPDF. 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-15569/ (Markdown: https://insights.sbomify.com/CVE-2025-15569/index.md)
```

## Sources

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

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