CVE-2025-62707: py-pdf pypdf · Excessive Iteration
Affects py-pdf pypdfSource CVE Database V5
Not known to be exploited · CVSS 6.6 Medium : upgrade to 6.1.3 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.1.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.
What to do
Upgrade py-pdf pypdf to 6.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIpypdfpkg:pypi/pypdfOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade all instances of pypdf to version 6.1.3 or later to ensure the vulnerability is patched. 2. Implement strict input validation and sanitization for all PDF files, especially those received from untrusted or external sources. 3. Employ sandboxing or resource limiting techniques when processing PDFs to prevent infinite loops from impacting critical systems. 4. Monitor application logs and system resource usage for signs of abnormal CPU consumption during PDF processing. 5. Where possible, isolate PDF processing services to minimize impact on other systems in case of exploitation. 6. Educate developers and system administrators about the vulnerability and ensure secure coding practices when integrating PDF libraries. 7. Regularly review and update third-party dependencies to incorporate security patches promptly.
Description
### Impact An attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires parsing the content stream of a page which has an inline image using the DCTDecode filter. ### Patches This has been fixed in [pypdf==6.1.3](https://github.com/py-pdf/pypdf/releases/tag/6.1.3). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [#3501](https://github.com/py-pdf/pypdf/pull/3501).