Quick answers
- Is CVE-2026-59936 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59936 being exploited in the wild.
- How severe is CVE-2026-59936?
- High severity, with a CVSS score of 4, published 8 July 2026.
- Which products and versions are affected?
- pypdf (PyPI) < 6.14.1, ECOSYSTEM:introduced=0,fixed=6.14.1.
- Is there a fix for CVE-2026-59936?
- Yes. pypdf (PyPI): upgrade to 6.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59936 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59936?
- Check whether you run 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.14.1 or later
pip install "pypdf>=6.14.1"
Technical details
A vulnerability exists in pypdf due to improper handling of inline images within a PDF content stream. Specifically, if an inline image is not properly terminated, the parser may enter an infinite loop (CWE-835) while attempting to process the stream, such as during text extraction. This is a resource consumption issue (CWE-400) that can be triggered remotely without authentication if the target application processes untrusted PDF files. The issue is resolved in version 6.14.1 by improving the termination logic for inline image parsing.
Affected products
- py-pdf pypdf < 6.14.1
Identifiers
- CVE-2026-59936
- GHSA-5xf7-4p34-54qr
- PYSEC-2026-3612
Timeline
- 2026-06-23: disclosed
- 2026-06-23: patched: Fix released in version 6.14.1
- 2026-07-23: advisory