Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-119208high7.1

pypdf: Possible long runtimes/large memory usage for encrypted PDF files

Impact

pypdf versions less than 6.21.3 may experience large runtimes or memory usage when accessing the page count of an encrypted PDF file with a wrong `/Count` value. An attacker can craft such a PDF. The impact is limited to resource consumption.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.
Applies when

This requires accessing the page count of an encrypted PDF file, which itself declares a wrong /Count value.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

pypdf PyPI
Affected range Recorded fix
Earlier releases before 6.21.3Ecosystem versions6.21.3

Version evidence: OSV · GHSA-62m5-6wh8-28x7

View original version evidence (125 explicit versions)

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

py-pdf · GitHub_M

pypdf

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

< 6.21.3

unaffected

unknown

Other versions: unknown

Original source description

Impact

An attacker who uses this vulnerability can craft a PDF which leads to large runtimes/memory usage. This requires accessing the page count of an encrypted PDF file, which itself declares a wrong /Count value.

Patches

This has been fixed in pypdf==6.21.3.

Workarounds

If you cannot upgrade yet, consider applying the changes from PR #4270.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-119208

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption

GitHub_M

Related →
Contributing organizations · 1
GitHub_M

Assigning organization

2026-10-29

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

6 sources