CVE-2026-103000 json
pypdf: Possible large memory usage when retrieving alphabetical page labels
published 2026-09-30 39 d ago modified 2026-11-02 6 d ago also GHSA-w23x-9jrw-r45c , PYSEC-2026-4160 , EUVD-2026-90283
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
pypdf is a free and open-source pure-python PDF library. Prior to 6.19.0, a crafted PDF can provide unusually large alphabetical page-label values that cause pypdf/_page_labels.py to generate strings beyond a reasonable page-label length when an application retrieves document page labels, consuming excessive memory and potentially making the application unavailable. This issue is fixed in version 6.19.0.
Patch / fix
- pypi pypdf 6.19.0
- py-pdf pypdf 6.19.0
- pypdf Debian 14 6.19.0-1
debian advisories DEBIAN-CVE-2026-103000
- github.com/py-pdf/pypdf@0d8b5a8 commit
- github.com/py-pdf/pypdf#4096 pull request
- github.com/py-pdf/pypdf/releases/tag/6.19.0 release
Vendor 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-103000 updated cvss 7.5
pypdf: pypdf: Denial of Service via large alphabetical page labels
-
Red Hat Lightspeed Core lightspeed-core/rag-tool-cpu-rhel9, lightspeed-core/lightspeed-stack-rhel9, lightspeed-core/rag-tool-cuda-12.9-rhel9affected: workaround, no fix available
-
Red Hat Ansible Automation Platform 2 ansible-automation-platform-25/lightspeed-chatbot-rhel8affected: workaround, no fix planned “Will not fix”
-
Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/bootc-gaudi-rhel9, rhelai3/disk-image-cuda-rhel9affected: workaround, no fix available, no fix planned “Will not fix”
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-ogx-core-rhel9, rhoai/odh-llama-stack-core-rhel9 Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9affected: workaround, no fix available
-
Red Hat Ansible Automation Orchestrator 2026 ansible-automation-platform/automation-orchestrator-backend-rhel9 Red Hat OpenShift Lightspeed openshift-lightspeed/lightspeed-ocp-rag-rhel9, openshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9not affected: vulnerable code not present
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
- yes
- Technical impact
- partial
- Assessed
- 39 d ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | 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 |
| CNA | 4.0 | 8.7 | 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: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 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pypdf | <6.19.0 |
6.19.0 |
Affected products
- py-pdf pypdf
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/py-pdf/pypdf/pull/4096
web, patch, issue-tracking
-
github.com
/py-pdf/pypdf/commit/0d8b5a8832cde1ba308b5c27567b879b7b7eed4a
web, patch
-
github.com
/py-pdf/pypdf/security/advisories/GHSA-w23x-9jrw-r45c
web, vendor-advisory
-
github.com
/py-pdf/pypdf/releases/tag/6.19.0
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-103000
advisory
-
github.com
/py-pdf/pypdf
package
-
pypi.org
/project/pypdf
package
-
github.com
/advisories/GHSA-w23x-9jrw-r45c
advisory
Sources
- CVE List CVE-2026-103000
- GitHub Advisory GHSA-w23x-9jrw-r45c
- NVD CVE-2026-103000
- OSV PYSEC-2026-4160
Fencer Vulns 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.