Skip to content
Fencer Intel
high 7.5

CVE-2026-102998 json

pypdf: Possible long runtimes when generating appearance streams

published last mo. modified 7d ago also EUVD-2026-90384 , GHSA-php9-fj8v-98fj , PYSEC-2026-4157

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 27%
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 with form field values can cause pypdf/generic/_appearance_stream.py appearance-stream generation to repeat invariant selection-data work inside a loop when an application updates fields with flattening enabled, resulting in excessive runtimes and application unavailability. This issue is fixed in version 6.19.0.

Patch / fix

  • pypi pypdf 6.19.0
  • py-pdf pypdf 6.19.0
  • pypdf2_project pypdf2 6.19.0
  • pypdf_project pypdf 6.19.0
  • pypdf Debian 14 6.19.0-1

debian advisories DEBIAN-CVE-2026-102998

Is CVE-2026-102998 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-102998 updated cvss 7.5

pypdf: pypdf: Denial of Service via crafted PDF form fields

  • Red Hat Lightspeed Core lightspeed-core/rag-tool-cpu-rhel9, lightspeed-core/lightspeed-stack-rhel9, lightspeed-core/rag-tool-cuda-12.9-rhel9
    affected: workaround, no fix available
  • Red Hat Ansible Automation Platform 2 ansible-automation-platform-25/lightspeed-chatbot-rhel8
    affected: 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-rhel9
    affected: 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
    affected: workaround, no fix available
  • Red Hat Quay 3.17 quay/quay-rhel9 1792072128
    fixed: vendor fix RHSA-2026:83822
  • Red Hat Quay 3.18 quay/quay-rhel9 1792172715
    fixed: vendor fix RHSA-2026:85980
  • 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-rhel9 Red Hat Quay 3.17 quay/clair-rhel9 1791849089, quay/quay-builder-rhel9 1792026771, quay/quay-rhel9-operator 1792071725, quay/quay-operator-bundle 1792085906, quay/quay-bridge-rhel9-operator 1791848775, quay/quay-bridge-operator-bundle 1791849552, +3 more Red Hat Quay 3.18 quay/clair-rhel9 1791846185, quay/quay-builder-rhel9 1792027151, quay/quay-rhel9-operator 1792172291, quay/quay-operator-bundle 1792178950, quay/quay-bridge-rhel9-operator 1791846163, quay/quay-bridge-operator-bundle 1791846837, +3 more
    not 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
last mo.

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% 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.19.0
6.19.0

Affected products

  • py-pdf pypdf

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.