Quick answers
- Is CVE-2026-24688 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24688 being exploited in the wild.
- How severe is CVE-2026-24688?
- Medium severity, with a CVSS score of 4.3, published 27 January 2026.
- Which products and versions are affected?
- pypdf (PyPI) ECOSYSTEM:introduced=0,fixed=6.6.2.
- Is there a fix for CVE-2026-24688?
- Yes. pypdf (PyPI): upgrade to 6.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24688 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-24688?
- Check whether you run Py-Pdf 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.6.2 or later
pip install "pypdf>=6.6.2"
Technical details
This vulnerability is a classic infinite loop condition (CWE-835) in pypdf's outline/bookmark processing logic. An attacker can craft a malicious PDF file with a circular or self-referential outline structure that causes the parsing code to enter an unreachable exit condition. The attack vector is local or network-based depending on how the PDF is obtained, and requires only that the application process the outlines/bookmarks of the PDF file—no authentication is needed. Successful exploitation causes a denial of service through resource exhaustion (CPU/process hang). The vulnerability is fixed in pypdf version 6.6.2 and later.
Affected products
- pypdf pypdf before 6.6.2
Identifiers
- CVE-2026-24688
- GHSA-2q4j-m29v-hq73
- PYSEC-2026-1827
Timeline
- 2026-01-26: disclosed
- 2026-01-26: patched: Fixed in version 6.6.2