PDF-processing hang via repeated recovery loop
Published Mar 26, 2026 · Updated Mar 27, 2026
An infinite loop in py-pdf pypdf before 6.9.2 allows attackers to hang PDF processing by supplying a crafted document. DictionaryObject.read_from_stream broadly catches parse errors in non-strict mode and retries after recursion or filter-limit failures without a usable exit path. The crafted file must be read with non-strict parsing, and the resulting loop interrupts the process performing the PDF operation.
Summary
What happened
An infinite loop in py-pdf pypdf before 6.9.2 allows attackers to hang PDF processing by supplying a crafted document. DictionaryObject.read_from_stream broadly catches parse errors in non-strict mode and retries after recursion or filter-limit failures without a usable exit path. The crafted file must be read with non-strict parsing, and the resulting loop interrupts the process performing the PDF operation.
The record
- CVE
- CVE-2026-33699
- Published
- Mar 26, 2026
- Updated
- Mar 27, 2026
- Vendor
- py-pdf
- Product
- pypdf
- Classifications
- CWE-835, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.9.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo