Skip to content
Fencer Intel
high 7.5

CVE-2026-102993 json

pypdf: Possible large memory usage when retrieving Roman page labels

published last mo. modified 7d ago also GHSA-qv6h-rv94-w285 , PYSEC-2026-4158 , EUVD-2026-90365

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

pypdf is a free and open-source pure-python PDF library. Prior to 6.17.0, a crafted PDF can provide unusually large Roman page-label values that cause pypdf/_page_labels.py to generate excessively large numeral strings when an application retrieves document page labels, consuming large amounts of memory and potentially making the application unavailable. This issue is fixed in version 6.17.0.

Patch / fix

  • pypi pypdf 6.17.0
  • py-pdf pypdf 6.17.0
  • pypdf Debian 14 6.19.0-1

debian advisories DEBIAN-CVE-2026-102993

Is CVE-2026-102993 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 Fencer

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-102993 updated cvss 6.5

pypdf: pypdf: Denial of Service via crafted Roman page labels

  • Red Hat Ansible Automation Orchestrator 2026 ansible-automation-platform/automation-orchestrator-backend-rhel9 Red Hat Lightspeed Core lightspeed-core/rag-tool-cpu-rhel9, lightspeed-core/lightspeed-stack-rhel9, lightspeed-core/rag-tool-cuda-12.9-rhel9 Red Hat OpenShift Lightspeed openshift-lightspeed/lightspeed-ocp-rag-rhel9, openshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9
    affected: workaround, no fix available “Update pypdf to version 6.17.0 or later. Until the update is applied, avoid processing untrusted PDF files and run PDF processing in a constrained environment with appropriate memory limits.”
  • Red Hat Ansible Automation Platform 2 ansible-automation-platform-25/lightspeed-chatbot-rhel8
    affected: workaround, no fix planned “Update pypdf to version 6.17.0 or later. Until the update is applied, avoid processing untrusted PDF files and run PDF processing in a constrained environment with appropriate memory limits.”
  • Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/bootc-gaudi-rhel9, rhelai3/disk-image-cuda-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-ogx-core-rhel9, rhoai/odh-llama-stack-core-rhel9
    affected: workaround, no fix available “Update pypdf to version 6.17.0 or later. Until the update is applied, avoid processing untrusted PDF files and run PDF processing in a constrained environment with appropriate memory limits.”
  • Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9
    affected: workaround, no fix available, no fix planned “Update pypdf to version 6.17.0 or later. Until the update is applied, avoid processing untrusted PDF files and run PDF processing in a constrained environment with appropriate memory limits.”

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
last mo.

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).

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.17.0
6.17.0

Affected products

  • py-pdf pypdf

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

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.