Skip to main content
CVE-2026-134366VulnerabilityPublished

pypdf before 7.0.0 contains a resource exhaustion vulnerability that allows attackers to cause large memory usage by

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134366· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 7.0.0 soon.

Data as of 21 Nov 2026, 19:28 UTC

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

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 7.0.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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 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 21 Nov 2026.

What to do

Upgrade pypdf to 7.0.0.

Affected software

ProductAffectedFixed in
py-pdfpypdfAffected
  • <7.0.0
Fixed in
  • 7.0.0
PyPIpypdfpkg:pypi/pypdfOther threatsAffected
  • <7.0.0
Fixed in
  • 7.0.0

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

AI-suggested

A fix is available in pypdf version 7.0.0 and later. Users should upgrade to version 7.0.0 or newer to remediate this vulnerability. No vendor advisory was provided to indicate alternative mitigations or temporary fixes.

Description

pypdf versions before 7.0.0 have a resource exhaustion vulnerability where crafted PDF cross-reference streams cause excessive memory usage. Attackers can create PDFs with cross-reference stream offsets all pointing to a single large object, leading to memory exhaustion during parsing.

References

Community reviews

Loading reviews…