How severe is GHSA-cj93-chg6-vgv8?

No CVSS score has been assigned to GHSA-cj93-chg6-vgv8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cj93-chg6-vgv8?

GHSA-cj93-chg6-vgv8 affects the following packages: pypdf (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-cj93-chg6-vgv8?

Update pypdf to 6.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cj93-chg6-vgv8 is resolved across your whole dependency graph.

How do I detect GHSA-cj93-chg6-vgv8 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 GHSA-cj93-chg6-vgv8 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 GHSA-cj93-chg6-vgv8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cj93-chg6-vgv8 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 GHSA-cj93-chg6-vgv8?

GHSA-cj93-chg6-vgv8 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th 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 GHSA-cj93-chg6-vgv8?

GHSA-cj93-chg6-vgv8 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cj93-chg6-vgv8 published, and has it been updated?

GHSA-cj93-chg6-vgv8 was published on June 12, 2026 and was last updated on September 10, 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

pypdf: Possible large memory usage for large offsets for layout mode textGHSA-cj93-chg6-vgv8

Fix: py-pdf/pypdf#3790

GHSA-cj93-chg6-vgv8 is a Uncontrolled Resource Consumption vulnerability in pypdf. A fix is available for pypdf — see the affected versions and patch details below.

Also known asCVE-2026-48155PYSEC-2026-3016

Published

Jun 12, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 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 GHSA-cj93-chg6-vgv8.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs7th percentile — riskier than 7% 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

Impact

An attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires extracting text in layout mode with large character offsets.

Patches

This has been fixed in pypdf==6.12.0.

Workarounds

If developers are unable to immediately upgrade, they should consider applying the changes from PR #3790.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

pypdfpypdf_project

< 6.12.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.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cj93-chg6-vgv8 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

This Moderate-impact flaw in pypdf can lead to a denial of service in Red Hat products that process untrusted PDF files. The vulnerability, triggered by specially crafted PDFs during text extraction with large character offsets, can cause excessive memory consumption. This affects Red Hat Quay, Red Hat Enterprise…

Workaround published by Red Hat

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.

Source: Red Hat security advisory for GHSA-cj93-chg6-vgv8 (CC BY 4.0)

Frequently Asked Questions

### Impact An attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires extracting text in layout mode with large character offsets. ### Patches This has been fixed in [pypdf==6.12.0](https://github.com/py-pdf/pypdf/releases/tag/6.12.0). ### Workarounds If developers are unable to immediately upgrade, they should consider applying the changes from PR [#3790](https://github.com/py-pdf/pypdf/pull/3790).

O3 Security · Impact-Aware SCA

Is GHSA-cj93-chg6-vgv8 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works