# CVE-2026-82035: PyMuPDF 1.28.2 Path Traversal via extract_objects() Font Branch

> Attackers can write arbitrary files outside the intended directory by supplying a crafted document with malicious font names to PyMuPDF.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-82035, GHSA-434w-92hw-f2m3, UBUNTU-CVE-2026-82035, openSUSE-SU-2026:11824-1, openSUSE-SU-2026:21912-1

## What is CVE-2026-82035?

CVE-2026-82035 is a high-severity path traversal vulnerability in PyMuPDF, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

PyMuPDF through 1.28.2, fixed in commit b2c8f3a, contains a path traversal vulnerability in the font branch of extract_objects() in src/__main__.py, where the output filename is constructed by joining a document-controlled BaseFont name directly onto the user-supplied output directory without stripping path separators or dot-dot sequences. Attackers can supply a crafted PDF, EPUB, XPS, or FB2 file with a BaseFont name containing encoded path separators that decode to ../ sequences or absolute paths, causing arbitrary file writes outside the intended output directory without requiring authentication or elevated privileges.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-PyMuPDF` | openSUSE:Leap 16.0 | All versions | 1.21.1-lp160.6.1 |
| `python-PyMuPDF` | openSUSE:Tumbleweed | All versions | 1.28.2-1.1 |

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

Apply the vendor's patch.

## Is CVE-2026-82035 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82035 is a high-severity path traversal vulnerability in PyMuPDF, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82035 in the wild and no public exploit code.

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

## Sources

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

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