Vulnerability · CVE-2026-119208
pypdf has possible long runtimes/large memory usage for encrypted PDF files
Published Oct 30, 2026 · catalog updated Oct 30, 2026 · pypdf has possible long
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-119208. EPSS is 0.22%. Act only if a listed version of pypdf has possible long is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (pypdf has possible long).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.22%
- Remediation
- Version ranges on file
- Affected products
- PyPI pypdf · pip pypdf · pypi pypdf
### Impact An attacker who uses this vulnerability can craft a PDF which leads to large runtimes/memory usage. This requires accessing the page count of an encrypted PDF file, which itself declares a wrong value. ### Patches This has been fixed in [pypdf==6.21.3](https://github.com/py-pdf/pypdf/releases/tag/6.21.3). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [#4270](https://github.com/py-pdf/pypdf/pull/4270).
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- PyPI pypdf0 → 6.21.3
- pip pypdf< 6.21.3
- pypi pypdfversion unspecified
How to fix CVE-2026-119208
Upgrade
CVE-2026-119208 lists a fix boundary at 6.21.3. Compare the installed build with that boundary before you change production.
Version check
Affected < 6.21.3
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-119208. EPSS is 0.22%. Act only if a listed version of pypdf has possible long is installed.
Which versions are affected?
Compare what you have installed with 0 → 6.21.3, < 6.21.3. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-400: Uncontrolled Resource Consumption; CWE-770: Allocation of Resources Without Limits or Throttling. EPSS 0.22%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 30, 2026 · GitHub Advisory Database
Detected
### Impact An attacker who uses this vulnerability can craft a PDF which leads to large runtimes/memory usage. This requires accessing the page count of an encrypted PDF file, which itself declares a wrong value. ### Patches This has been fixed in [pypdf==6.21.3](https://github.com/py-pdf/pypdf/releases/tag/6.21.3). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [
Oct 30, 2026 · GitHub Advisory Database
Updated
### Impact An attacker who uses this vulnerability can craft a PDF which leads to large runtimes/memory usage. This requires accessing the page count of an encrypted PDF file, which itself declares a wrong value. ### Patches This has been fixed in [pypdf==6.21.3](https://github.com/py-pdf/pypdf/releases/tag/6.21.3). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [
Oct 30, 2026 · PyPA Advisory Database
Fix available
pypdf fixed in 6.21.3
Oct 30, 2026 · PyPA Advisory Database
Fix available
pypdf fixed in 6.21.3
Oct 30, 2026 · PyPA Advisory Database
Updated
### Impact An attacker who uses this vulnerability can craft a PDF which leads to large runtimes/memory usage. This requires accessing the page count of an encrypted PDF file, which itself declares a wrong value. ### Patches This has been fixed in [pypdf==6.21.3](https://github.com/py-pdf/pypdf/releases/tag/6.21.3). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [
Sources
- CVE.orgVulnerability recordCVE-2026-119208
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-119208
30-day exploitation probability 0.22%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-62m5-6wh8-28x7
pypdf has possible long runtimes/large memory usage for encrypted PDF files
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-119208
An attacker who uses this vulnerability can craft a PDF which leads to large runtimes/memory usage. This requires accessing the page count of an encrypted PDF file, which itself declares a wrong /Count value.
advisories.gitlab.com - PyPA Advisory DatabasePackage advisoryGHSA-62m5-6wh8-28x7
pypdf has possible long runtimes/large memory usage for encrypted PDF files
osv.dev
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 6, 2026
- GitHub Advisory DatabaseNov 6, 2026
- GitLab Advisory DatabaseNov 3, 2026
- PyPA Advisory DatabaseNov 2, 2026
- CVE.orgOct 31, 2026