CVE-2026-84311: pypdf: Possible long runtimes/large memory usage when extracting XForm objects
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: py-pdf pypdf 6.16.1.
Low priority for now. Upgrade to py-pdf pypdf 6.16.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
pypdf is a free and open-source pure-python PDF library. Prior to 6.16.1, an attacker can craft a PDF that causes pypdf/_page.py PageObject._extract_text and PageObject.extract_xform_text to traverse a directed acyclic graph of reused form XObjects in which each form invokes a child multiple times, creating exponentially many traversal paths and causing long runtimes and large memory consumption. This issue is fixed in version 6.16.1.
- Published
- Sep 1, 2026
- Updated
- Nov 2, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-834
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 4.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| py-pdf | pypdf | cpe:2.3:a:py-pdf:pypdf |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
py-pdf pypdf
- < 6.16.1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- py-pdf pypdfbefore 6.16.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pypdf | from 0 | — |
| Debian:12 | pypdf2 | from 0 | — |
| Debian:14 | pypdf | before 6.19.0-1 | 6.19.0-1 |
| PyPI | pypdf | before 6.16.1 | 6.16.1 |
Same product
py-pdf: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-103000pypdf: Possible large memory usage when retrieving alphabetical page labels34Monitor
- CVE-2026-102999pypdf: Possible long runtimes with large amount of embedded files34Monitor
- CVE-2026-102998pypdf: Possible long runtimes when generating appearance streams34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-84309Sep 1, 2026 · pypdf: Possible infinite loop for TreeObject.insert_child27Monitor
- ← EarlierCVE-2026-84310Sep 1, 2026 · pypdf: Possible long runtimes/large memory usage when retrieving outlines19Monitor
- Later →CVE-2026-102993Sep 30, 2026 · pypdf: Possible large memory usage when retrieving Roman page labels34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| py-pdf pypdf | 6.16.1 · description | Vendor (CNA) |
| debian:pypdf | 6.19.0-1 · Debian:14 | Package registry (OSV) |
| PyPI:pypdf | 6.16.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-11558052 days apartpypdf: Possible long runtimes for large xref table header limits28Monitor
- CVE-2026-41168132 days apartpypdf has possible long runtimes for wrong size values in cross-reference and object streams27Monitor
- CVE-2026-27025193 days apartpypdf has possible long runtimes/large memory usage for large /ToUnicode streams27Monitor
- CVE-2025-62707314 days apartpypdf affected by possible infinite loop when reading DCT inline images without EOF marker26Monitor
- CVE-2026-4815696 days apartpypdf: Possible long runtimes for zero-only width values in cross-reference streams20Monitor
- CVE-2026-7185225 days apartpypdf: Possible long runtimes/large memory usage for large CID font width ranges19Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-834 · Excessive IterationCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.