Skip to main content
VulnerabilityPublished Updated

CVE-2026-71870: py-pdf pypdf · Uncontrolled Resource Consumption

Affects py-pdf pypdfSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to 6.15.0 when convenient.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.15.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

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

What to do

Upgrade py-pdf pypdf to 6.15.0.

Affected software

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

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

AI-suggested

Upgrade to pypdf version 6.15.0 or later, where this vulnerability is fixed. No other mitigation or workaround is documented. Patch status is confirmed fixed in 6.15.0.

Description

pypdf is a free and open-source pure-python PDF library. Prior to 6.15.0, a crafted PDF can cause large memory consumption when pypdf/_cmap.py function parse_bfrange parses unusually large source-code or destination-string tokens in a font /ToUnicode CMap during text extraction. This issue is fixed in 6.15.0.

References

Community reviews

Loading reviews…