dbcve.org
CWE-426Weakness · CWE-426

CVE-2025-15569

HIGH · 7.0 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MuPDF versions up to 1.26.1 on Windows contain an uncontrolled search path vulnerability in the get_system_dpi function within platform/x11/win_main.c. This allows a local attacker to potentially place malicious DLLs in directories searched by the application, leading to arbitrary code execution.

MitigationUpgrade MuPDF to version 1.26.2 to remediate this vulnerability. As a defense-in-depth measure, ensure the application runs from trusted directories and that the PATH is controlled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if MuPDF is installed on Windows
    Search for mupdf.exe in common installation directories such as C:\Program Files\MuPDF, C:\Program Files (x86)\MuPDF, or check the application menu. Also search the system using: Get-ChildItem -Path C:\ -Recurse -Filter mupdf.exe -ErrorAction SilentlyContinue
    Affected if MuPDF executable is found on the Windows system
  2. Determine the installed MuPDF version
    Run 'mupdf.exe --version' from the command line in the directory where mupdf.exe is located, or right-click mupdf.exe, select Properties, and view the Details tab for the Product version
    Affected if Version displays as 1.26.1 or lower, or version cannot be determined but MuPDF is present
  3. Verify the Windows platform
    Confirm the operating system is Windows. Run 'systeminfo | findstr /B /C:"OS Name"' or check system properties. This vulnerability affects only Windows builds of MuPDF
    Affected if Running on Windows and the vulnerable binary is present
  4. Check if the vulnerable code path exists in the executable
    If possible, use a hex editor or strings tool to search within mupdf.exe for the function name 'get_system_dpi' or examine the platform/x11/win_main.c source file if available in the build
    Affected if The get_system_dpi function is present in the win_main.c code and the version is 1.26.1 or lower

If MuPDF version 1.26.1 or lower is installed on Windows, the system is affected by this uncontrolled search path vulnerability in the get_system_dpi function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MuPDF to version 1.26.2 to remediate this vulnerability. As a defense-in-depth measure, ensure the application runs from trusted directories and that the PATH is controlled.

Recommended fix High confidence

MuPDF 1.26.2

  1. 1. Download MuPDF version 1.26.2 from the official Artifex distribution source (artifex.com or the official MuPDF download page)
  2. 2. Verify the downloaded package integrity using checksums if provided
  3. 3. Uninstall or remove the existing vulnerable MuPDF installation
  4. 4. Install the version 1.26.2 package following standard installation procedures
  5. 5. Verify the installed version is 1.26.2 by checking the application version information

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15569 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data