Skip to main content
Menu
CVEs

pypdf denial of service via XFA form handling

Affects pypdf 2.4.2 before 7.0.0 when loading XFA forms with many (possibly small) fields. Fixed in 7.0.0.

CVE-2026-134367Published 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 2.4.2 before 7.0.0 contains a resource exhaustion vulnerability in its handling of XFA forms that allows attackers to cause excessive memory consumption. Attackers can supply a crafted PDF containing XFA forms with many small fields so that loading the forms consumes large amounts of memory, causing a denial of service.

Who should check

Teams running pypdf from PyPI (2.4.2 up to 7.0.0) to load PDFs, especially those accepting untrusted PDFs with XFA forms.

“Affecting pypdf >= 2.4.2, < 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-134367 (pypdf 2.4.2 before 7.0.0 Excessive Memory Usage via XFA Forms), 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-134367 (entry last updated 2026-11-21):
Affected:
- PyPI package pypdf: from 2.4.2, fixed in 7.0.0
Fixed versions: 7.0.0.
Conditions (all must be true for the bug to be hit):
- pypdf versions from 2.4.2 before 7.0.0 (source: https://www.vulncheck.com/advisories/pypdf-2.4.2-before-7.0.0-excessive-memory-usage-via-xfa-forms)
- Loading XFA forms containing many (possibly small) fields (source: https://github.com/py-pdf/pypdf/security/advisories/GHSA-cmpx-464x-82c3)
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-134367 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134367 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-cmpx-464x-82c3
- https://www.vulncheck.com/advisories/pypdf-2.4.2-before-7.0.0-excessive-memory-usage-via-xfa-forms
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-134367
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-134367"}.

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-cmpx-464x-82c3
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134367
RecordNVD · CVE-2026-134367
Other links 1
Linkvulncheck.com · advisories/pypdf-2.4.2-before-7.0.0-excessive-memory-usage-via-xfa-forms

Questions about CVE-2026-134367

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

Loading a PDF with XFA forms that contain many, possibly small, fields causes excessive memory consumption, which can lead to a denial of service.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134367?

pypdf (PyPI): from 2.4.2 before 7.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

pypdf versions from 2.4.2 before 7.0.0 are in the affected range, and the issue requires loading XFA forms with many (possibly small) fields. To check a version, run pip show pypdf or print pypdf.__version__ and compare the result with 7.0.0.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134367?

Upgrade pypdf to 7.0.0 or later, which is the fixed version listed for this vulnerability.

Source: vulncheck.com, github.com

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