# CVE-2026-25880: Untrusted Search Path in SumatraPDF Reader (explorer.exe on Windows)

> Attackers can execute arbitrary code by placing a malicious binary in the PDF directory, triggering execution when users view the file location.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Feb 2026
- **Updated:** 10 Feb 2026
- **Also known as:** GHSA-5x4h-247q-px37

## What is CVE-2026-25880?

CVE-2026-25880 is a high-severity path traversal vulnerability in sumatrapdfreader sumatrapdf, published on 9 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

SumatraPDF is a multi-format reader for Windows. In 3.5.2 and earlier, the PDF reader allows execution of a malicious binary (explorer.exe) located in the same directory as the opened PDF when the user clicks File → “Show in folder”. This behavior leads to arbitrary code execution on the victim’s system with the privileges of the current user, without any warning or user interaction beyond the menu click.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2026-25880?

It affects 1 product.


Products: Sumatrapdfreader Sumatrapdf.

## How do I fix CVE-2026-25880?

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

## Is CVE-2026-25880 being exploited?

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

## Other vulnerabilities in sumatrapdfreader sumatrapdf

- [CVE-2012-4895](https://insights.sbomify.com/CVE-2012-4895/): Memory corruption in n/a (critical 9.3)
- [CVE-2012-4896](https://insights.sbomify.com/CVE-2012-4896/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4117](https://insights.sbomify.com/CVE-2009-4117/): Memory corruption in n/a (critical 9.3)
- [CVE-2026-23512](https://insights.sbomify.com/CVE-2026-23512/): SumatraPDF has an Untrusted Search Path in sumatrapdf/src/AppTools.cpp (high 8.6)
- [CVE-2013-2830](https://insights.sbomify.com/CVE-2013-2830/): Use after free in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25880 and fix it if it is affected.

What it is: CVE-2026-25880 is a high-severity path traversal vulnerability in sumatrapdfreader sumatrapdf, published on 9 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-25880 in the wild and no public exploit code.

Affected product: sumatrapdfreader sumatrapdf. 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-2026-25880/ (Markdown: https://insights.sbomify.com/CVE-2026-25880/index.md)
```

## Sources

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

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