Skip to main content
Menu
CVEs

pypdf memory exhaustion in PDF cross-reference stream parsing

Affects pypdf before 7.0.0 when a PDF's cross-reference stream has all its offsets pointing to one large object. Fixed in 7.0.0.

CVE-2026-134366Published November 21, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.0.0
Who is exposed
Not reported

Summary

Written by a model

pypdf before 7.0.0 contains a resource exhaustion vulnerability that allows attackers to cause large memory usage by supplying crafted PDF cross-reference streams. Attackers can craft a PDF whose cross-reference stream offsets all point to one large object, exhausting memory in applications parsing the file.

Who should check

Teams running pypdf before 7.0.0 that parse PDFs, including services handling untrusted or uploaded PDF files.

“Affecting pypdf < 7.0.0”

vulncheck.com

What to do

Upgrade to a fixed version: 7.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134366 (pypdf before 7.0.0 Memory Exhaustion via Cross-Reference Streams with Identical Offsets), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134366 (entry last updated 2026-11-21):
Affected:
- PyPI package pypdf: fixed in 7.0.0
Fixed versions: 7.0.0.
Conditions (all must be true for the bug to be hit):
- pypdf versions before 7.0.0 (source: https://www.vulncheck.com/advisories/pypdf-before-7.0.0-memory-exhaustion-via-cross-reference-streams-with-identical-offsets)
- The PDF must contain a cross-reference stream whose offsets all point to one large object (source: https://github.com/py-pdf/pypdf/security/advisories/GHSA-59jv-x5x2-gg4c)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134366 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134366 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/py-pdf/pypdf/security/advisories/GHSA-59jv-x5x2-gg4c
- https://www.vulncheck.com/advisories/pypdf-before-7.0.0-memory-exhaustion-via-cross-reference-streams-with-identical-offsets
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134366
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134366"}.

Affected versions

cve.now Index

46Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach20/20pypdf: 49.3M downloads a week
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 91 if added to CISA KEV
  • Would score about 86 if CISA's SSVC rates exploitation active
  • Would score about 51 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · py-pdf/pypdf · Advisory GHSA-59jv-x5x2-gg4c
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134366
RecordNVD · CVE-2026-134366
Other links 1
Linkvulncheck.com · advisories/pypdf-before-7.0.0-memory-exhaustion-via-cross-reference-streams-with-identical-offsets

Questions about CVE-2026-134366

Is CVE-2026-134366 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A crafted PDF cross-reference stream can make pypdf use a large amount of memory, which can exhaust memory in applications that parse the file and cause a denial of service.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134366?

pypdf (PyPI): before 7.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of pypdf before 7.0.0 are affected. The triggering condition is a PDF whose cross-reference stream has all of its offsets pointing to one large object. To check the installed version, run pip show pypdf or print pypdf.__version__.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134366?

Upgrade pypdf to version 7.0.0 or later, which is the fixed version in the product range.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.