cve.bz

CVE-2026-113786 py-pdf pypdf: Permissive List of Allowed Inputs

2.3 lowEPSS 0.4%Fix available

Low (2.3) in py-pdf pypdf. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in pypdf 6.21.1.

On this page
pypdf is a free and open-source pure-python PDF library. Prior to 6.21.1, an attacker can craft a PDF containing image data labeled with the /DCTDecode filter that causes Pillow to select and invoke an unintended image parser when the image is loaded. Environments without the optional Pillow dependency are not affected. This issue is fixed in version 6.21.1.

Severity

CVSS 4.0

2.3 low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-183 Permissive List of Allowed Inputs
OWASP Top 10
A05:2025 Injection, A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-113786 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113786?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113786?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-113786 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
py-pdf pypdf< 6.21.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5hx5-vpf9-5wcvPyPIpypdf<6.21.16.21.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12pypdf, pypdf2no fix listedDEBIAN-CVE-2026-113786
Debian13pypdfno fix listedDEBIAN-CVE-2026-113786
Debian14pypdf6.21.1-1DEBIAN-CVE-2026-113786
Ubuntu20.04:LTS, 22.04:LTS, Pro:16.04:LTS and 1 morepypdf2no fix listedUBUNTU-CVE-2026-113786
Ubuntu24.04:LTSpypdf, pypdf2no fix listedUBUNTU-CVE-2026-113786
Ubuntu26.04:LTS, 26.10pypdfno fix listedUBUNTU-CVE-2026-113786
openSUSELeap 16.0python-pypdf6.19.0-bp160.2.1openSUSE-SU-2026:22188-1
openSUSETumbleweedpython-pypdf6.21.2-1.1openSUSE-SU-2026:12306-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This vulnerability is rated Low impact because exploitation is limited to a localized denial of service during document parsing, requiring an attacker to supply a specially crafted file to an environment with the optional Pillow image library active. In Red Hat environments such as OpenShift AI, Lightspeed, and Quay, pypdf operates as an internal backend component, meaning an attack only disrupts the immediate processing task rather than compromising underlying host confidentiality or integrity. Furthermore, deployments that do not invoke image extraction workflows or lack the optional image processing dependency remain unaffected.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Ansible Automation Orchestrator 2026ansible-automation-platform/automation-orchestrator-backend-rhel9Fix deferred
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Fix deferred
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Fix deferred
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Fix deferred
OpenShift Lightspeedopenshift-lightspeed/lightspeed-ocp-rag-rhel9Fix deferred
OpenShift Lightspeedopenshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Out of support scope
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/disk-image-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-llama-stack-core-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-ogx-core-rhel9Fix deferred
Red Hat Quay 3quay/quay-rhel8Out of support scope
Red Hat Quay 3quay/quay-rhel9Out of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-113786.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON