How many CVEs have patched _sanitize_pdf15_xref_stream_index_pairs?

2 published CVEs changed _sanitize_pdf15_xref_stream_index_pairs in py-pdf/pypdf, in 4 distinct patches totalling 72 changed lines, between 2026 and 2026.

What is the latest CVE that changed _sanitize_pdf15_xref_stream_index_pairs?

CVE-2026-48156 (pypdf: Possible long runtimes for zero-only width values in cross-reference streams), published 2026-05-28, changed lines 1092 to 1100 of pypdf/_reader.py.

How does _sanitize_pdf15_xref_stream_index_pairs compare to the rest of py-pdf/pypdf?

py-pdf/pypdf has 52 CVEs with a located fix in total; 2 of them changed _sanitize_pdf15_xref_stream_index_pairs.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

py-pdf/pypdf

Function

_sanitize_pdf15_xref_stream_index_pairs

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

pypdf/_reader.py

Last patched May 28, 2026

2

CVEs

That changed this function

4

Distinct patches

Backports counted once

72

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_sanitize_pdf15_xref_stream_index_pairs in py-pdf/pypdf was changed by 2 published CVE fixes in 2026, in 4 distinct patches that added or removed 72 lines in total.

py-pdf/pypdf has 52 CVEs with a located fix in total, so 4% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _sanitize_pdf15_xref_stream_index_pairs, newest first, with the lines each fix touched.

pypdf: Possible long runtimes for zero-only width values in cross-reference streams
CVE-2026-48156 · lines 1092–1100 · +9 −3
Medium · CVSS 5.1
EPSS 0.2%2026-05-28
pypdf has possible long runtimes for wrong size values in cross-reference and object streams
CVE-2026-41168 · lines 1052–1115 · +50 −10
Medium · CVSS 6.9
EPSS 0.5%2026-04-22

Get an alert when the next CVE fix lands in py-pdf/pypdf, with the patched functions.

Monitor pypdf CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

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

decode5 CVEs · pypdf/filters.py _decompress_with_limit4 CVEs · pypdf/filters.py decompress3 CVEs · pypdf/filters.py _get_outline3 CVEs · pypdf/_doc_common.py _flatten3 CVEs · pypdf/_doc_common.py _extract_text3 CVEs · pypdf/_page.py

All patched functions in py-pdf/pypdf

Frequently asked questions

Common questions about CVE fixes to _sanitize_pdf15_xref_stream_index_pairs.

How many CVEs have patched _sanitize_pdf15_xref_stream_index_pairs?: 2 published CVEs changed _sanitize_pdf15_xref_stream_index_pairs in py-pdf/pypdf, in 4 distinct patches totalling 72 changed lines, between 2026 and 2026.
What is the latest CVE that changed _sanitize_pdf15_xref_stream_index_pairs?: CVE-2026-48156 (pypdf: Possible long runtimes for zero-only width values in cross-reference streams), published 2026-05-28, changed lines 1092 to 1100 of pypdf/_reader.py.
How does _sanitize_pdf15_xref_stream_index_pairs compare to the rest of py-pdf/pypdf?: py-pdf/pypdf has 52 CVEs with a located fix in total; 2 of them changed _sanitize_pdf15_xref_stream_index_pairs.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

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