pypdf has possible large memory usage for exceptions in strict mode
CVE-2026-119207
Impact An attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires loading an invalid dictionary. Patches This has been fixed in [pypdf==6.21.3](https://github.com/py-pdf/pypdf/releases/tag/6.21.3). Workarounds If you cannot upgrade yet, consider applying the changes from PR [#4265](https://github.com/py-pdf/pypdf/pull/4265).
Assessment
- CVSS
- 7.1 (v4.0)
- Severity
- High
- EPSS
- 0.00304% chance of exploitation in the next 30 days
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 30 October 2026
- Last updated
- 30 October 2026
- Affected
- pip · pypdf
- Weakness
- CWE-400, CWE-405
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
At the source
References
- https://github.com/py-pdf/pypdf/security/advisories/GHSA-4vqv-7265-gm2w
- https://nvd.nist.gov/vuln/detail/CVE-2026-119207
- https://github.com/py-pdf/pypdf/pull/4265
- https://github.com/py-pdf/pypdf/commit/64270258c0eced720f7960aecf8cef31afd39f8d
- https://github.com/py-pdf/pypdf/releases/tag/6.21.3
- https://github.com/advisories/GHSA-4vqv-7265-gm2w
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-119207