VulnerabilityPublished 14 Sep 2026Updated 17 Oct 2026

CVE-2026-82035: PyMuPDF through 1.28.2, fixed

Affects pymupdfSource GCVE Database

Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-434w-92hw-f2m3

What to do

Affected software

Product	Affected	Fixed in
PyPIpymupdf`pkg:pypi/pymupdf`Other threats	Affected <=1.28.2	Fixed in–
Ubuntu 20.04 LTSpymupdf`pkg:deb/ubuntu/pymupdf?arch=source&distro=focal`Other threats	Affected =1.16.11-1	Fixed in–
Ubuntu 22.04 LTSpymupdf`pkg:deb/ubuntu/pymupdf?arch=source&distro=jammy`Other threats	Affected =1.17.4+ds1-2build2 =1.17.4+ds1-2build3 =1.19.2+ds1-1ubuntu1	Fixed in–
Ubuntu 24.04 LTSpymupdf`pkg:deb/ubuntu/pymupdf?arch=source&distro=noble`Other threats	Affected 1.22.5+ds1-1 – 1.23.7+ds1-1ubuntu2 5 affected builds	Fixed in–
Ubuntu 26.10pymupdf`pkg:deb/ubuntu/pymupdf?arch=source&distro=stonking`Other threats	Affected =1.26.7+ds1-1build1	Fixed in–
Ubuntu 26.04 LTSpymupdf`pkg:deb/ubuntu/pymupdf?arch=source&distro=resolute`Other threats	Affected =1.25.4+ds1-4 =1.26.7+ds1-1 =1.26.7+ds1-1build1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability is available and was implemented in commit b2c8f3a. Users should upgrade PyMuPDF to a version that includes this commit to remediate the issue. Since this is not a cloud service, remediation requires updating the affected software. No additional mitigation steps are indicated by the vendor advisory.

Description

PyMuPDF versions through 1.28.2 contain a path traversal vulnerability in the font branch of the extract_objects() function. This flaw allows an attacker to craft malicious document files with specially encoded BaseFont names that decode to directory traversal sequences or absolute paths, enabling arbitrary file writes outside the intended output directory without authentication or elevated privileges. The vulnerability was fixed in a commit identified as b2c8f3a.

Impact

An attacker can write arbitrary files outside the intended output directory by exploiting the path traversal vulnerability in the extract_objects() function. This can lead to unauthorized file creation or modification, potentially impacting system integrity. No authentication or elevated privileges are required to exploit this vulnerability. The CVSS v3.1 score is 7.1 (medium severity), indicating a significant impact on integrity with low attack complexity and no privileges required.

CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Oct 2026, 02:29 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats