Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
pypdf versions before 6.1.3 can be made to use large amounts of memory. An attacker who supplies a crafted PDF can trigger this when the content stream of a page using the LZWDecode filter is parsed, so a user opening or processing such a file is affected. Upgrade to pypdf 6.1.3 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.6 | Medium | 4.0 | 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:U | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0044, the 38th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 22 Oct 2025, 22:15 UTC Confirmed by NVD
- 31 Oct 2026, 14:34 UTC First seen by agentprime
- 31 Oct 2026, 14:34 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-jfx9-29x2-rv3j
- OSV: GHSA-jfx9-29x2-rv3j
- github.com/py-pdf/pypdf/security/advisories/GHSA-jfx9-29x2-rv3j
- nvd.nist.gov/vuln/detail/CVE-2025-62708
- github.com/py-pdf/pypdf/pull/3502
- github.com/py-pdf/pypdf/commit/e51d07807ffcdaf18077b9486dadb3dc05b368da
- github.com/py-pdf/pypdf
- github.com/py-pdf/pypdf/releases/tag/6.1.3