Skip to main content
VulnerabilityPublished

CVE-2026-119208: pypdf has possible long runtimes/large memory usage for encrypted PDF files

Affects pypdfSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119208· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 6.21.3 soon.

Data as of 31 Oct 2026, 01:53 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.07.1
Patch
Available – fixed in 6.21.3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade pypdf to 6.21.3.

Affected software

ProductAffectedFixed in
PyPIpypdfAffected
  • <6.21.3
Fixed in
  • 6.21.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### 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 `/Count` 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).

References

Community reviews

Loading reviews…