Security Resilience

CVE-2026-119207

DoS in Py-Pdf Pypdf ≤ 6.21.3

Published
29 October 2026
Modified
02 November 2026
Patch / advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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
EPSS Score 0.0022 13th percentile
Risk Priority 55 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-119207 is a high-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Py-Pdf Pypdf. Its CVSS base score is 7.1 (High).

Operationally, ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

pypdf is a free and open-source pure-python PDF library. Prior to 6.21.3, pypdf can consume excessive memory when strict mode loads a crafted invalid PDF dictionary. Nested parsing failures add repeated exception text to newly raised errors, allowing a small…

more

malformed dictionary to amplify into very large error messages. This issue is fixed in version 6.21.3.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-27888Same product: Py-Pdf Pypdf
CVE-2026-28351Same product: Py-Pdf Pypdf
CVE-2026-119204Same product: Py-Pdf Pypdf
CVE-2026-119208Same product: Py-Pdf Pypdf
CVE-2026-103000Same product: Py-Pdf Pypdf
CVE-2026-22690Same product: Py-Pdf Pypdf
CVE-2026-49461Same product: Py-Pdf Pypdf
CVE-2026-57204Same product: Py-Pdf Pypdf
CVE-2026-102995Same product: Py-Pdf Pypdf
CVE-2026-102996Same product: Py-Pdf Pypdf

Affected Assets

py-pdf
pypdf
≤ 6.21.3

Mitigating Controls

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-400 CWE-405

Alternate site allows resumption of operations if resource exhaustion at the primary site is exploited to cause unavailability.

addresses: CWE-400 CWE-405

Alternate telecommunications services enable resumption of essential functions when primary services become unavailable due to uncontrolled resource consumption.

addresses: CWE-400 CWE-405

Alternate paths allow continued C2 operations when an attacker exploits resource-consumption weaknesses against the primary channel.

addresses: CWE-400 CWE-405

Directly limits uncontrolled resource consumption that leads to denial-of-service.

addresses: CWE-400 CWE-405

Directly mitigates uncontrolled consumption by enforcing allocation limits/quotas that preserve availability for legitimate use.

addresses: CWE-400

Limiting concurrent sessions directly prevents uncontrolled resource consumption by capping the number of active sessions per user or account.

addresses: CWE-400

Analysis identifies uncontrolled resource consumption indicative of denial-of-service or abuse attempts.

addresses: CWE-400

Contingency plan testing includes resource exhaustion scenarios to verify recovery, making it harder for attackers to sustain exploits that cause uncontrolled consumption.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

finds

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

blocks

Monitoring network service usage and applying controls to restrict access when necessary limits an attacker’s ability to consume excessive resources through unrestricted or unauthenticated service calls.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-400, a class-level weakness. Rules are authored against its narrower children: CWE-770.
  • No fine-grained STIG row for CWE-405, a class-level weakness. Rules are authored against its narrower children: CWE-1050.

References