Skip to main content
Menu
CVEs

pypdf placeholder data leak in encrypted PDF templates

Affects pypdf 3.7.1 before 7.0.0 when encrypted templated PDFs are involved. Fixed in 7.0.0.

CVE-2026-134364Published 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 3.7.1 before 7.0.0 contains an information disclosure vulnerability that allows attackers to guess placeholders in encrypted templated documents by analyzing file identifiers. Attackers with a document sharing the same template and access to other documents' file identifiers can recover placeholder contents from encrypted PDFs.

Who should check

Teams running pypdf from 3.7.1 up to (not including) 7.0.0 from PyPI that handle encrypted templated PDFs.

“Affecting pypdf >= 3.7.1, < 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-134364 (pypdf 3.7.1 before 7.0.0 Placeholder Recovery via File Identifier in Encrypted Documents), 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-134364 (entry last updated 2026-11-21):
Affected:
- PyPI package pypdf: from 3.7.1, fixed in 7.0.0
Fixed versions: 7.0.0.
Conditions (all must be true for the bug to be hit):
- Affects pypdf 3.7.1 before 7.0.0. (source: https://www.vulncheck.com/advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents)
- Encrypted templated documents are involved. (source: https://github.com/py-pdf/pypdf/security/advisories/GHSA-mwj3-fpmc-hjcv)
- Attacker needs a document with the same template and access to the file identifier of other documents. (source: https://github.com/py-pdf/pypdf/security/advisories/GHSA-mwj3-fpmc-hjcv)
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-134364 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134364 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-mwj3-fpmc-hjcv
- https://www.vulncheck.com/advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents
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-134364
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-134364"}.

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-mwj3-fpmc-hjcv
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134364
RecordNVD · CVE-2026-134364
Other links 1
Linkvulncheck.com · advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents

Questions about CVE-2026-134364

Is CVE-2026-134364 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?

An attacker who has a document with the same template and access to the file identifier of other documents can recover placeholder contents from encrypted PDFs. This is an information disclosure flaw.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134364?

pypdf (PyPI): from 3.7.1 before 7.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

The flaw affects pypdf 3.7.1 before 7.0.0 when encrypted templated documents are involved. To check an installed version, run pip show pypdf.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134364?

Upgrade pypdf to 7.0.0 or later, the version that fixes this issue.

Source: vulncheck.com, github.com

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