How severe is CVE-2026-102993?

No CVSS score has been assigned to CVE-2026-102993 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-102993?

CVE-2026-102993 affects the following packages: pypdf (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-102993?

Update pypdf to 6.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-102993 is resolved across your whole dependency graph.

How do I detect CVE-2026-102993 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pypdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-102993 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2026-102993 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-102993 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-102993?

CVE-2026-102993 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-102993?

CVE-2026-102993 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-770 (CWE-770). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-102993 published, and has it been updated?

CVE-2026-102993 was published on September 30, 2026 and was last updated on October 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-102993 — pypdf

Fix: py-pdf/pypdf@89db7c4

CVE-2026-102993 is a Uncontrolled Resource Consumption vulnerability in pypdf. A fix is available for pypdf — see the affected versions and patch details below.

pypdf: Possible large memory usage when retrieving Roman page labels

Also known asGHSA-qv6h-rv94-w285PYSEC-2026-4158

Published

Sep 30, 2026

Updated

Oct 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-102993.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk-0.17%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍pypdf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pypdf`	all versions	6.17.0`pip install --upgrade 'pypdf==6.17.0'`

Affected Products

1 product · 1 configurations

Application

pypdfpypdf_project

< 6.17.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pypdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pypdf to 6.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-102993 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat is aware of a denial-of-service vulnerability in pypdf. A crafted PDF can cause excessive memory consumption when page labels are processed.

Workaround published by Red Hat

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.

Source: Red Hat security advisory for CVE-2026-102993 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-102993 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works