CVE-2026-115572: pypdf: Possible long runtimes for repeated references to the same missing object
pypdf can be made to run for a very long time by a PDF that references the same missing indirect object many times. The result is a denial of service in any service that parses untrusted PDFs. Fixed in pypdf 6.21.2.
Published Oct 23, 2026 · Analysis Nov 2, 2026
What an attacker can do
The trigger is a PDF where the same indirect object, one that does not exist in the file, is referenced repeatedly. The advisory says the problem appears when pypdf loads the relevant parts of the file, such as its pages. The release notes for 6.21.2 list a security fix named "Avoid repeated full file loads" (PR 4240), which the advisory names as the workaround patch. That matches the cause: each repeated lookup of the missing object appears to trigger a new full read of the file. The release notes do not state this link directly.
An attacker only needs to get a crafted PDF to a service that opens it with pypdf, for example an upload form, a document-ingestion pipeline for an LLM or a mail attachment scanner. The CVSS 4.0 vector shows network attack, no privileges, passive user interaction and only an availability impact. One worker can be tied up per file, so a handful of uploads can starve a small worker pool.
Who is affected
pip package pypdf older than 6.21.2. It matters when your code opens untrusted PDFs and reads their pages, for example in an upload handler or ingestion job. Check the installed version with:
pip show pypdfpypdf
- Ecosystem
- PyPI
- Affected
- < 6.21.2
- Fixed in
- 6.21.2
- Check
pip show pypdf
How to fix it
Upgrade to pypdf 6.21.2.
pip install --upgrade "pypdf>=6.21.2"If you cannot upgrade yet, the advisory suggests applying the changes from pull request 4240. Also run PDF parsing with a time limit and a memory cap, for example in a subprocess you can kill.
How to tell if you were hit
Look for PDF-handling workers pinned at high CPU for long periods, and for requests that time out right after a PDF upload. Keep the offending file and check it for many repeated references to an object number that has no definition.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Impact
An attacker who uses this vulnerability can craft a PDF which leads to long runtimes. This requires loading relevant parts of a file (like their pages) where the same, but non-existent indirect object is referenced multiple times.
Patches
This has been fixed in pypdf==6.21.2.
Workarounds
If you cannot upgrade yet, consider applying the changes from PR #4240.
Credited to manop55555.
Questions
- Does this give code execution or data access?
No. The advisory describes only long runtimes, so the impact is availability.
- How is this different from the xref table issue in the same release?
This one needs repeated references to the same missing object. The other (CVE-2026-115580) comes from large or wrong upper limits in the xref table header. Both are fixed in 6.21.2.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-119203
pypdf has possible infinite loop when hitting EOF in standard xref table during trailer search
high7.1Oct 30, 2026CVE-2026-119204
pypdf has possible large memory usage when parsing page tree
high7.1Oct 30, 2026CVE-2026-119205
pypdf has possible infinite loop when cloning dictionaries
high7.1Oct 30, 2026CVE-2026-119206
pypdf has possible long runtimes when retrieving page labels
high7.1Oct 30, 2026CVE-2026-119207
pypdf has possible large memory usage for exceptions in strict mode
high7.1Oct 30, 2026CVE-2026-119208
pypdf has possible long runtimes/large memory usage for encrypted PDF files
high7.1Oct 30, 2026
