Update dependency pypdf to v6.6.0 [SECURITY] #1828
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==6.1.3→==6.6.0GitHub Vulnerability Alerts
CVE-2025-66019
Impact
An attacker who uses this vulnerability can craft a PDF which leads to a memory usage of up to 1 GB per stream. This requires parsing the content stream of a page using the LZWDecode filter.
This is a follow up to GHSA-jfx9-29x2-rv3j to align the default limit with the one for zlib.
Patches
This has been fixed in pypdf==6.4.0.
Workarounds
If users cannot upgrade yet, use the line below to overwrite the default in their code:
CVE-2026-22690
Impact
An attacker who exploits this vulnerability can craft a PDF which leads to possibly long runtimes for actually invalid files. This can be achieved by omitting the
/Rootentry in the trailer, while using a rather large/Sizevalue. Only the non-strict reading mode is affected.Patches
This has been fixed in pypdf==6.6.0.
Workarounds
Resources
This issue has been fixed in #3594.
CVE-2026-22691
Impact
An attacker who exploits this vulnerability can craft a PDF which leads to possibly long runtimes for invalid
startxrefentries. When rebuilding the cross-reference table, PDF files with lots of whitespace characters become problematic. Only the non-strict reading mode is affected.Patches
This has been fixed in pypdf==6.6.0.
Workarounds
Resources
This issue has been fixed in #3594.
pypdf's LZWDecode streams be manipulated to exhaust RAM
CVE-2025-66019 / GHSA-m449-cwjh-6pw7
More information
Details
Impact
An attacker who uses this vulnerability can craft a PDF which leads to a memory usage of up to 1 GB per stream. This requires parsing the content stream of a page using the LZWDecode filter.
This is a follow up to GHSA-jfx9-29x2-rv3j to align the default limit with the one for zlib.
Patches
This has been fixed in pypdf==6.4.0.
Workarounds
If users cannot upgrade yet, use the line below to overwrite the default in their code:
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:UReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
pypdf has possible long runtimes for malformed startxref
CVE-2026-22691 / GHSA-4f6g-68pf-7vhv
More information
Details
Impact
An attacker who exploits this vulnerability can craft a PDF which leads to possibly long runtimes for invalid
startxrefentries. When rebuilding the cross-reference table, PDF files with lots of whitespace characters become problematic. Only the non-strict reading mode is affected.Patches
This has been fixed in pypdf==6.6.0.
Workarounds
Resources
This issue has been fixed in #3594.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:UReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
pypdf has possible long runtimes for missing /Root object with large /Size values
CVE-2026-22690 / GHSA-4xc4-762w-m6cg
More information
Details
Impact
An attacker who exploits this vulnerability can craft a PDF which leads to possibly long runtimes for actually invalid files. This can be achieved by omitting the
/Rootentry in the trailer, while using a rather large/Sizevalue. Only the non-strict reading mode is affected.Patches
This has been fixed in pypdf==6.6.0.
Workarounds
Resources
This issue has been fixed in #3594.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:UReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
py-pdf/pypdf (pypdf)
v6.6.0Compare Source
Security (SEC)
Deprecations (DEP)
New Features (ENH)
Bug Fixes (BUG)
Robustness (ROB)
Documentation (DOC)
Developer Experience (DEV)
Maintenance (MAINT)
Full Changelog
v6.5.0Compare Source
New Features (ENH)
Robustness (ROB)
Developer Experience (DEV)
Full Changelog
v6.4.2Compare Source
New Features (ENH)
Robustness (ROB)
Developer Experience (DEV)
Full Changelog
v6.4.1Compare Source
Bug Fixes (BUG)
Robustness (ROB)
Documentation (DOC)
Full Changelog
v6.4.0Compare Source
Security (SEC)
New Features (ENH)
Robustness (ROB)
Full Changelog
v6.3.0Compare Source
Security (SEC)
New Features (ENH)
Robustness (ROB)
Full Changelog
v6.2.0Compare Source
New Features (ENH)
Bug Fixes (BUG)
Full Changelog
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.