pypdf: Inefficient handling of non-whitespace inputs in read_until_whitespace
### Impact An attacker who uses this vulnerability can craft a PDF which leads to long runtimes. This requires a call to `read_until_whitespace` with an input which does not have whitespace for a long time. ### Patches This has been fixed in [pypdf==6.15.0](https://github.com/py-pdf/pypdf/releases/tag/6.15.0). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [#3947](https://github.com/py-pdf/pypdf/pull/3947).
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-82398US | medium5.3 | — | ||
pypdf is a free and open-source pure-python PDF library. Prior to 6.15.0, an attacker can craft a PDF that causes long runtimes when the pypdf/_utils.py function read_until_whitesp… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-fc8x-2rww-xw9mADVISORY
- https://github.com/py-pdf/pypdfPACKAGE
- https://github.com/py-pdf/pypdf/commit/4959848e057e37c218dccad7465259210923faaaWEB
- https://github.com/py-pdf/pypdf/pull/3947WEB
- https://github.com/py-pdf/pypdf/releases/tag/6.15.0WEB
- https://github.com/py-pdf/pypdf/security/advisories/GHSA-fc8x-2rww-xw9mWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-82398ADVISORY
- https://pypi.org/project/pypdfPACKAGE
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan