CVE-2026-59938
No exploitation reported by the sources we read.
- Published2026-07-08
- Fixed in6.14.0
- WeaknessCWE-789
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
pypdf is a free and open-source pure-python PDF library. Prior to 6.14.0, an attacker can craft a PDF with declared image size values that are much too large compared to the actual data, causing large memory usage in pypdf image parsing. This issue is fixed in version 6.14.0.
Timeline
dates in UTC- 2026-07-0818:16CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-59938?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-59938?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.14 | < 6.14.0 | 6.14.0 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
pypdf: pypdf: Possible large memory usage for wrong image dimensions
exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence · openshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9 as a component of OpenShift Lightspeed · openshift-lightspeed/lightspeed-ocp-rag-rhel9 as a component of OpenShift Lightspeed · +8 more
Fix
- Update Pypdf project pypdf to 6.14.0
- Workaround from the vendor Red Hat Product Security CVE-2026-59938 · 11 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
- No fix available, says the vendor Red Hat Product Security CVE-2026-59938 · 11 productsFix deferred
Advisories and patches
- github.comPatch
- github.comPatch
- github.comRelease Notes
- github.comPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- CISA-ADPSSVC decisionnone2026-07-09
- OpenCVESSVC decisionnone—
- CNACVSS 4.06.9read 2026-10-23
- NVDCVSS 3.15.3read 2026-10-23
- CNAweakness (CWE)CWE-789read 2026-10-23
- FIRST EPSSEPSS score0.5 %2026-10-22
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CVSS 4.0 vector
- 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:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2026-07-08
- Last Modified
- 2026-07-09
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-5qjq-93h5-hrgp
Frequently asked questions
What is CVE-2026-59938?
Is CVE-2026-59938 actively exploited?
What is the CVSS score for CVE-2026-59938?
Running pypdf? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.