pypdf 6.21.2
PkgFire would install this release with a warning.·Checked 11 hours ago·Published 21 October 2026
Why
-
warnVulnerability
pypdf has possible long runtimes when retrieving page labels (fixed in 6.21.3)
-
warnVulnerability
pypdf has possible large memory usage for exceptions in strict mode (fixed in 6.21.3)
-
warnVulnerability
pypdf has possible infinite loop when hitting EOF in standard xref table during trailer search (fixed in 6.21.4)
-
warnVulnerability
pypdf has possible long runtimes/large memory usage for encrypted PDF files (fixed in 6.21.3)
-
warnVulnerability
pypdf has possible large memory usage when parsing page tree (fixed in 6.21.4)
-
warnVulnerability
pypdf has possible infinite loop when cloning dictionaries (fixed in 6.21.4)
-
warnVulnerability
pypdf has possible large memory usage when parsing cross-reference streams (fixed in 6.21.3)
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Not signed
- Build provenance
- Attested
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.