CVE-2026-41312 json
pypdf: Manipulated FlateDecode predictor parameters can exhaust RAM
published 6mo ago modified 7d ago also EUVD-2026-25112 , GHSA-7gw9-cf7v-778f , PYSEC-2026-3011
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
pypdf is a free and open-source pure-python PDF library. An attacker who uses a vulnerability present in versions prior to 6.10.2 can craft a PDF which leads to the RAM being exhausted. This requires accessing a stream compressed using `/FlateDecode` with a `/Predictor` unequal 1 and large predictor parameters. This has been fixed in pypdf 6.10.2. As a workaround, one may apply the changes from the patch manually.
Patch / fix
- pypi pypdf 6.10.2
- py-pdf pypdf 6.10.2
- pypdf2_project pypdf2 6.10.2
- pypdf_project pypdf 6.10.2
- pypdf Debian 14 6.19.0-1
debian advisories DEBIAN-CVE-2026-41312
- python-pypdf openSUSE Tumbleweed 6.10.2-2.1
opensuse advisories openSUSE-SU-2026:10658-1
Is CVE-2026-41312 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-41312 updated cvss 5.5
pypdf: pypdf: Denial of Service due to excessive memory consumption via specially crafted PDF
-
Red Hat Lightspeed Core lightspeed-core/rag-tool-rhel9 Red Hat OpenShift Lightspeed openshift-lightspeed/lightspeed-ocp-rag-rhel9, openshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9 Red Hat Ansible Automation Platform 2 ansible-automation-platform-25/lightspeed-chatbot-rhel8 Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/disk-image-cuda-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-llama-stack-core-rhel9 Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/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 |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pypdf | <6.10.2 |
6.10.2 |
Affected products
- py-pdf pypdf
Classification
- Weakness
-
- CWE-789 Memory Allocation with Excessive Size Value
References
-
github.com
/py-pdf/pypdf/pull/3734
web, issue-tracking, patch
-
github.com
/py-pdf/pypdf/commit/ac734dab4eef92bcce50d503949b4d9887d89f11
web, patch
-
github.com
/py-pdf/pypdf/security/advisories/GHSA-7gw9-cf7v-778f
web, patch, vendor-advisory
-
github.com
/py-pdf/pypdf/releases/tag/6.10.2
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-41312
advisory
-
github.com
/py-pdf/pypdf
package
-
pypi.org
/project/pypdf
package
-
github.com
/advisories/GHSA-7gw9-cf7v-778f
advisory
Sources
- CVE List CVE-2026-41312
- GitHub Advisory GHSA-7gw9-cf7v-778f
- NVD CVE-2026-41312
- OSV PYSEC-2026-3011
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.