How many CVEs have patched modification_date_raw?

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

What is the latest CVE that changed modification_date_raw?

CVE-2026-84311 (pypdf: Possible long runtimes/large memory usage when extracting XForm objects), published 2026-09-01, changed lines 242 of pypdf/_doc_common.py.

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

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

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

modification_date_raw

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

pypdf/_doc_common.py

Last patched September 1, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

4

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

modification_date_raw in py-pdf/pypdf was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 4 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 modification_date_raw, newest first, with the lines each fix touched.

pypdf: Possible long runtimes/large memory usage when extracting XForm objects
CVE-2026-84311 · line 242 · +1 −1
Medium · CVSS 4.8
EPSS 0.1%2026-09-01
pypdf: Possible long runtimes/large memory usage when retrieving outlines
CVE-2026-84310 · line 242 · +1 −1
Medium · CVSS 4.8
EPSS 0.1%2026-09-01

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 modification_date_raw.

How many CVEs have patched modification_date_raw?: 2 published CVEs changed modification_date_raw in py-pdf/pypdf, in 2 distinct patches totalling 4 changed lines, between 2026 and 2026.
What is the latest CVE that changed modification_date_raw?: CVE-2026-84311 (pypdf: Possible long runtimes/large memory usage when extracting XForm objects), published 2026-09-01, changed lines 242 of pypdf/_doc_common.py.
How does modification_date_raw compare to the rest of py-pdf/pypdf?: py-pdf/pypdf has 52 CVEs with a located fix in total; 2 of them changed modification_date_raw.
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