Linux
pypdf security updates
Patch Radar has 69 security fixes for pypdf, closing 67 CVEs. The newest security fix is DEBIAN-CVE-2026-115580 (6.21.4-1), released November 6, 2026.
Latest version
n/a
Release date not known
Security fixes
69
On record in Patch Radar
CVEs
67
Closed by those fixes
Exploited
0
Vendor report or CISA KEV
Security fixes, newest first
| Priority | Fix | Release | Fixed in | CVEs | Exploited | Released |
|---|---|---|---|---|---|---|
| Routine | DEBIAN-CVE-2026-115580 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-115585 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-115572 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-119209 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-119203 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-119204 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-119205 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-119206 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-119207 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-119208 | Debian 14 | 6.21.4-1 | 1 | Nov 6, 2026 | |
| Routine | DEBIAN-CVE-2026-113786 | Debian 14 | 6.21.1-1 | 1 | Oct 24, 2026 | |
| Routine | DEBIAN-CVE-2026-113794 | Debian 14 | 6.21.0-1 | 1 | Oct 24, 2026 | |
| Routine | DEBIAN-CVE-2026-113795 | Debian 14 | 6.21.0-1 | 1 | Oct 24, 2026 | |
| Routine | DEBIAN-CVE-2026-113793 | Debian 14 | 6.21.0-1 | 1 | Oct 24, 2026 | |
| Routine | DEBIAN-CVE-2026-113792 | Debian 14 | 6.21.0-1 | 1 | Oct 24, 2026 | |
| Routine | DEBIAN-CVE-2026-113789 | Debian 14 | 6.21.0-1 | 1 | Oct 24, 2026 | |
| Routine | DEBIAN-CVE-2026-113791 | Debian 14 | 6.21.0-1 | 1 | Oct 24, 2026 | |
| Routine | DEBIAN-CVE-2026-113790 | Debian 14 | 6.21.0-1 | 1 | Oct 24, 2026 | |
| High | DEBIAN-CVE-2026-103000 | Debian 14 | 6.19.0-1 | 1 | Oct 4, 2026 | |
| High | DEBIAN-CVE-2026-102999 | Debian 14 | 6.19.0-1 | 1 | Oct 4, 2026 | |
| High | DEBIAN-CVE-2026-102993 | Debian 14 | 6.19.0-1 | 1 | Oct 4, 2026 | |
| High | DEBIAN-CVE-2026-102994 | Debian 14 | 6.19.0-1 | 1 | Oct 4, 2026 | |
| High | DEBIAN-CVE-2026-102995 | Debian 14 | 6.19.0-1 | 1 | Oct 4, 2026 | |
| High | DEBIAN-CVE-2026-102996 | Debian 14 | 6.19.0-1 | 1 | Oct 4, 2026 | |
| High | DEBIAN-CVE-2026-102997 | Debian 14 | 6.19.0-1 | 1 | Oct 4, 2026 | |
| High | DEBIAN-CVE-2026-102998 | Debian 14 | 6.19.0-1 | 1 | Oct 4, 2026 | |
| Routine | DEBIAN-CVE-2026-84311 | Debian 14 | 6.19.0-1 | 1 | Sep 1, 2026 | |
| Routine | DEBIAN-CVE-2026-84310 | Debian 14 | 6.19.0-1 | 1 | Sep 1, 2026 | |
| Routine | DEBIAN-CVE-2026-84309 | Debian 14 | 6.19.0-1 | 1 | Sep 1, 2026 | |
| Routine | DEBIAN-CVE-2026-82398 | Debian 14 | 6.19.0-1 | 1 | Aug 31, 2026 | |
| Routine | DEBIAN-CVE-2026-71870 | Debian 14 | 6.19.0-1 | 1 | Aug 7, 2026 | |
| Routine | DEBIAN-CVE-2026-71852 | Debian 14 | 6.19.0-1 | 1 | Aug 7, 2026 | |
| High | DEBIAN-CVE-2026-59936 | Debian 14 | 6.19.0-1 | 1 | Jul 8, 2026 | |
| High | DEBIAN-CVE-2026-59935 | Debian 14 | 6.19.0-1 | 1 | Jul 8, 2026 | |
| Routine | DEBIAN-CVE-2026-59938 | Debian 14 | 6.19.0-1 | 1 | Jul 8, 2026 | |
| High | DEBIAN-CVE-2026-59937 | Debian 14 | 6.19.0-1 | 1 | Jul 8, 2026 | |
| Routine | DEBIAN-CVE-2026-57204 | Debian 14 | 6.19.0-1 | 1 | Jun 30, 2026 | |
| Routine | DEBIAN-CVE-2026-54531 | Debian 14 | 6.19.0-1 | 1 | Jun 22, 2026 | |
| Routine | DEBIAN-CVE-2026-54530 | Debian 14 | 6.19.0-1 | 1 | Jun 22, 2026 | |
| Routine | DEBIAN-CVE-2026-49461 | Debian 14 | 6.19.0-1 | 1 | Jun 22, 2026 | |
| Routine | DEBIAN-CVE-2026-54651 | Debian 14 | 6.19.0-1 | 1 | Jun 22, 2026 | |
| Routine | DEBIAN-CVE-2026-49460 | Debian 14 | 6.19.0-1 | 1 | Jun 22, 2026 | |
| Routine | DEBIAN-CVE-2026-48735 | Debian 14 | 6.19.0-1 | 1 | May 28, 2026 | |
| Routine | DEBIAN-CVE-2026-48156 | Debian 14 | 6.19.0-1 | 1 | May 28, 2026 | |
| Routine | DEBIAN-CVE-2026-48155 | Debian 14 | 6.19.0-1 | 1 | May 28, 2026 | |
| Routine | DEBIAN-CVE-2026-41314 | Debian 14 | 6.19.0-1 | 1 | Apr 22, 2026 | |
| Routine | DEBIAN-CVE-2026-41312 | Debian 14 | 6.19.0-1 | 1 | Apr 22, 2026 | |
| Routine | DEBIAN-CVE-2026-41313 | Debian 14 | 6.19.0-1 | 1 | Apr 22, 2026 | |
| Routine | DEBIAN-CVE-2026-41168 | Debian 14 | 6.19.0-1 | 1 | Apr 22, 2026 | |
| Routine | DEBIAN-CVE-2026-40260 | Debian 14 | 6.19.0-1 | 1 | Apr 17, 2026 | |
| High | DEBIAN-CVE-2026-33699 | Debian 14 | 6.9.2-1 | 1 | Mar 27, 2026 | |
| Routine | DEBIAN-CVE-2026-33123 | Debian 14 | 6.9.2-1 | 1 | Mar 20, 2026 | |
| Routine | DEBIAN-CVE-2026-31826 | Debian 14 | 6.9.0-1 | 1 | Mar 10, 2026 | |
| Routine | DEBIAN-CVE-2026-28804 | Debian 14 | 6.9.0-1 | 1 | Mar 6, 2026 | |
| Routine | DEBIAN-CVE-2026-28351 | Debian 14 | 6.9.0-1 | 1 | Feb 27, 2026 | |
| High | DEBIAN-CVE-2026-27888 | Debian 14 | 6.9.0-1 | 1 | Feb 26, 2026 | |
| High | DEBIAN-CVE-2026-27628 | Debian 14 | 6.9.0-1 | 1 | Feb 25, 2026 | |
| Routine | DEBIAN-CVE-2026-27026 | Debian 14 | 6.9.0-1 | 1 | Feb 20, 2026 | |
| Routine | DEBIAN-CVE-2026-27025 | Debian 14 | 6.9.0-1 | 1 | Feb 20, 2026 | |
| Routine | DEBIAN-CVE-2026-27024 | Debian 14 | 6.9.0-1 | 1 | Feb 20, 2026 | |
| Routine | DEBIAN-CVE-2026-24688 | Debian 14 | 6.9.0-1 | 1 | Jan 27, 2026 | |
| Routine | DEBIAN-CVE-2026-22691 | Debian 14 | 6.9.0-1 | 1 | Jan 10, 2026 | |
| Routine | DEBIAN-CVE-2026-22690 | Debian 14 | 6.9.0-1 | 1 | Jan 10, 2026 | |
| High | DEBIAN-CVE-2025-62708 | Debian 14 | 6.9.0-1 | 1 | Oct 22, 2025 | |
| High | DEBIAN-CVE-2025-62707 | Debian 14 | 6.9.0-1 | 1 | Oct 22, 2025 | |
| High | DEBIAN-CVE-2025-55197 | Debian 14 | 6.9.0-1 | 1 | Aug 13, 2025 | |
| Routine | DEBIAN-CVE-2023-36464 | Debian 12.15 (bookworm) | 3.4.1-1+deb12u1 | 1 | Jun 27, 2023 | |
| Routine | DEBIAN-CVE-2023-36464 | Debian 13.5 (trixie) | 3.17.4-1 | 1 | Jun 27, 2023 | |
| Routine | DEBIAN-CVE-2023-36464 | Debian 14 | 3.17.4-1 | 1 | Jun 27, 2023 |
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.