How many CVEs have a located fix in py-pdf/pypdf?

52 published CVEs have a fix traced to functions in py-pdf/pypdf, touching 106 functions across 28 files.

Which function in py-pdf/pypdf has been patched by the most CVEs?

decode in pypdf/filters.py has been changed by 5 CVE fixes, from 2025 to 2026.

How large is a typical CVE fix in py-pdf/pypdf?

The median fix changes 46 lines. 21% of fixes change 20 lines or fewer, and 23% change a single function.

How is a fix located to a function?

The upstream fix commit for each CVE is fetched and its diff is split into hunks. Each hunk is attributed to the function, method or type it changes, using the definition the diff itself names. Backports of the same fix to stable branches are counted once.

RadicalNotion.AI

Log in Create an account

python

#77 of 500 repositories

py-pdf/pypdf

Name: py-pdf/pypdf: functions patched by CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Functions and files changed by CVE fixes in this repository.

Latest located fix September 30, 2026

52

CVE fixes located

Published CVEs

106

Functions patched

Distinct function sites

28

Files patched

Distinct source files

2023–2026

Years covered

By CVE publication date

Overview

52 published CVEs have a fix traced to functions in py-pdf/pypdf, the earliest published in 2023. Those fixes changed 106 distinct functions across 28 files, in 749 patch hunks.

Among the 500 repositories tracked here, py-pdf/pypdf ranks #77 by the number of CVEs with a located fix.

Most patched functions

Functions in py-pdf/pypdf changed by the most CVE fixes.

Most patched files

Files in py-pdf/pypdf changed by the most CVE fixes.

1pypdf/filters.py13 CVEs · 5 functions
2pypdf/_reader.py9 CVEs · 14 functions
3pypdf/generic/_data_structures.py9 CVEs · 9 functions
4pypdf/_doc_common.py8 CVEs · 6 functions
5pypdf/_page.py5 CVEs · 5 functions
6pypdf/_writer.py4 CVEs · 6 functions
7pypdf/_utils.py4 CVEs · 2 functions
8pypdf/_cmap.py3 CVEs · 5 functions
9pypdf/generic/_image_xobject.py3 CVEs · 2 functions
10pypdf/generic/_image_inline.py2 CVEs · 6 functions

Fix size

How much code a CVE fix in py-pdf/pypdf changes, with backports counted once.

46

Median lines changed

Added plus removed, per CVE

21%

Fixes of 20 lines or fewer

Share of CVE fixes

23%

Fixes in a single function

Share of CVE fixes

Latest CVEs

The most recently published CVEs with a fix located in py-pdf/pypdf, and the functions each fix changed.

pypdf: Possible large memory usage when retrieving alphabetical page labels
CVE-2026-103000number2uppercase_roman_numeral number2uppercase_letter
High · CVSS 8.7
EPSS 0.3%2026-09-30
pypdf: Possible long runtimes with large amount of embedded files
CVE-2026-102999_get_attachment_contents _names _load
High · CVSS 8.7
EPSS 0.3%2026-09-30
pypdf: Possible long runtimes when generating appearance streams
CVE-2026-102998_glyph_id_to_bytes
High · CVSS 8.7
EPSS 0.3%2026-09-30
pypdf: Possible long runtimes for partially malformed FlateDecode streams (Follow-up)
CVE-2026-102997decompress
High · CVSS 8.7
EPSS 0.3%2026-09-30
pypdf: Possible large memory usage when parsing font data
CVE-2026-102996__check_entry_count Font _collect_tt_t1_character_widths
High · CVSS 8.7
EPSS 0.3%2026-09-30
pypdf: Possible large memory usage for large /ToUnicode streams (Follow-up 2)
CVE-2026-102995parse_bfchar process_cm_line
High · CVSS 8.7
EPSS 0.3%2026-09-30
pypdf: Possible long runtimes/large memory usage when parsing indirect objects
CVE-2026-102994read_part create_string_object read_until_whitespace
High · CVSS 8.7
EPSS 0.3%2026-09-30
pypdf: Possible large memory usage when retrieving Roman page labels
CVE-2026-102993roman_num number2uppercase_roman_numeral get_label_from_nums
High · CVSS 8.7
EPSS 0.4%2026-09-30
pypdf: Possible long runtimes/large memory usage when extracting XForm objects
CVE-2026-84311_extract_text__xform _extract_text _get_outline
Medium · CVSS 4.8
EPSS 0.1%2026-09-01
pypdf: Possible long runtimes/large memory usage when retrieving outlines
CVE-2026-84310_extract_text__xform _extract_text _get_outline
Medium · CVSS 4.8
EPSS 0.1%2026-09-01
pypdf: Possible infinite loop for TreeObject.insert_child
CVE-2026-84309insert_child
Medium · CVSS 6.9
EPSS 0.2%2026-09-01
pypdf: Inefficient handling of non-whitespace inputs in read_until_whitespace
CVE-2026-82398read_until_whitespace
Medium · CVSS 6.9
EPSS 0.5%2026-08-31

Get an alert for each new py-pdf/pypdf CVE, with the patched functions and AI-written analysis.

Monitor pypdf CVEs

Other repositories

Repositories with a similar number of located CVE fixes.

debian/qemu52 CVEs wordpress/wordpress52 CVEs froxlor/froxlor53 CVEs grokability/snipe-it53 CVEs dataease/dataease51 CVEs fusionpbx/fusionpbx51 CVEs patriksimek/vm251 CVEs gogs/gogs54 CVEs

Browse all repositories

Frequently asked questions

Common questions about CVE fixes in py-pdf/pypdf.

How many CVEs have a located fix in py-pdf/pypdf?: 52 published CVEs have a fix traced to functions in py-pdf/pypdf, touching 106 functions across 28 files.
Which function in py-pdf/pypdf has been patched by the most CVEs?: decode in pypdf/filters.py has been changed by 5 CVE fixes, from 2025 to 2026.
How large is a typical CVE fix in py-pdf/pypdf?: The median fix changes 46 lines. 21% of fixes change 20 lines or fewer, and 23% change a single function.
How is a fix located to a function?: The upstream fix commit for each CVE is fetched and its diff is split into hunks. Each hunk is attributed to the function, method or type it changes, using the definition the diff itself names. Backports of the same fix to stable branches are counted once.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track py-pdf/pypdf CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing