CVE-2026-102996 — pypdf
Fix: py-pdf/pypdf@0fb26ebCVE-2026-102996 is a Uncontrolled Resource Consumption vulnerability in pypdf. A fix is available for pypdf — see the affected versions and patch details below.
pypdf: Possible large memory usage when parsing font data
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-102996.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
pypdfReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
pypdf is a free and open-source pure-python PDF library. Prior to 6.18.1, a crafted PDF can provide a TrueType or Type1 simple font with an unusually large /Widths array, causing pypdf/_font.py Font._collect_tt_t1_character_widths to process entries beyond the 256 character codes meaningful for a simple font and consume excessive memory during operations such as text extraction. This issue is fixed in version 6.18.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pypdf | all versions | 6.18.1pip install --upgrade 'pypdf==6.18.1' |
Affected Products
pypdfpy-pdfDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pypdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pypdf to 6.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-102996 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This Important impact flaw can exhaust memory when a Red Hat service extracts text from a crafted PDF with an oversized font width array.
Mitigation 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.Source: Red Hat security advisory for CVE-2026-102996 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift AI 3.5 | rhoai/odh-ogx-core-rhel9:1793383222 | RHSA-2026:95872 |
| Red Hat Quay 3.10 | quay/quay-rhel8:1793993674 | RHSA-2026:99025 |
| Red Hat Quay 3.12 | quay/quay-rhel8:1793993854 | RHSA-2026:99027 |
| Red Hat Quay 3.14 | quay/quay-rhel8:1793993848 | RHSA-2026:99024 |
| Red Hat Quay 3.15 | quay/quay-rhel8:1793993771 | RHSA-2026:99023 |
| Red Hat Quay 3.16 | quay/quay-rhel9:1793993799 | RHSA-2026:99022 |
| Red Hat Quay 3.17 | quay/quay-rhel9:1793993778 | RHSA-2026:99026 |
| Red Hat Quay 3.18 | quay/quay-rhel9:1793993890 | RHSA-2026:99019 |
Frequently Asked Questions
Is CVE-2026-102996 in your dependencies?
Find it across PyPI, including transitive dependencies.