Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The pypdf Python package, versions before 6.21.3, can be made to run for a long time or use large amounts of memory when processing an encrypted PDF. An attacker would need to supply a crafted encrypted PDF whose declared page count value is wrong, and the impact occurs when the page count is read. The fix is to upgrade to pypdf 6.21.3; the source also suggests applying the changes from PR #4270 if an upgrade is not yet possible.
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 |
|---|---|---|---|---|
| 7.1 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0022, the 12th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 29 Oct 2026, 20:41 UTC Confirmed by the CVE List
- 29 Oct 2026, 21:17 UTC Confirmed by NVD
- 31 Oct 2026, 14:07 UTC First seen by agentprime
- 31 Oct 2026, 14:07 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-62m5-6wh8-28x7
- OSV: GHSA-62m5-6wh8-28x7
- github.com/py-pdf/pypdf/security/advisories/GHSA-62m5-6wh8-28x7
- nvd.nist.gov/vuln/detail/CVE-2026-119208
- github.com/py-pdf/pypdf/pull/4270
- github.com/py-pdf/pypdf/commit/82b91951dc74496bb3efe6465434f041bb6a5e6b
- github.com/py-pdf/pypdf
- github.com/py-pdf/pypdf/releases/tag/6.21.3