Quick answers
- Is CVE-2026-119208 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119208 being exploited in the wild.
- How severe is CVE-2026-119208?
- High severity, with a CVSS score of 4, published 29 October 2026.
- Which products and versions are affected?
- Pypdf before 6.21.3; pypdf (PyPI) < 6.21.3, ECOSYSTEM:introduced=0,fixed=6.21.3.
- Is there a fix for CVE-2026-119208?
- Yes. pypdf (PyPI): upgrade to 6.21.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119208 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119208?
- Check whether you run Pypdf or pypdf (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pypdf (PyPI): upgrade to 6.21.3 or later
pip install "pypdf>=6.21.3"
Technical details
The vulnerability exists in the get_num_pages() function, which returns the unvalidated /Count value from encrypted PDFs without walking the actual page tree, even after decryption. An attacker can craft an encrypted PDF with a forged /Count value that is much larger than the actual number of pages, causing subsequent operations like page_labels generation to allocate excessive memory. The fix validates the page count by walking the page tree after successful decryption rather than trusting the declared count.
Affected products
- pypdf pypdf before 6.21.3
Identifiers
- CVE-2026-119208
- GHSA-62m5-6wh8-28x7
Timeline
- 2026-10-27: patched
- 2026-10-29: disclosed