Quick answers
- Is CVE-2026-115585 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115585 being exploited in the wild.
- How severe is CVE-2026-115585?
- High severity, with a CVSS score of 4, published 23 October 2026.
- Which products and versions are affected?
- Py-Pdf Pypdf prior to 6.21.2; pypdf (PyPI) < 6.21.2, ECOSYSTEM:introduced=0,fixed=6.21.2.
- Is there a fix for CVE-2026-115585?
- Yes. pypdf (PyPI): upgrade to 6.21.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115585 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115585?
- 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.21.2 or later
pip install "pypdf>=6.21.2"
Technical details
The vulnerability is an incomplete remediation for handling repeated malformed cross-reference entries (CVE-2026-115585 references GHSA-55h5-xmcq-c37v). Even when a recovery cache is present, the library still triggers a complete PDF stream reload on each recovery attempt, leading to algorithmic complexity attacks. The fix involves caching invalid object lookups and reading the cross-reference table buffer only once during recovery.
Affected products
- py-pdf pypdf prior to 6.21.2
Identifiers
- CVE-2026-115585
- GHSA-jr96-gvgh-j3r4
Timeline
- 2026-10-23: disclosed
- 2026-10-21: patched