Summary
FPDI: Memory Exhaustion and Endless Loop in FPDI leads to Denial of Service
Workarounds
No.
References
No.
Impact
This is a significant Denial of Service (DoS) vulnerability. Any application that uses FPDI to process user-supplied PDF files is at risk. An attacker can upload a small, malicious PDF file that will cause the server-side script to crash due to memory exhaustion or a script time-out. Repeated attacks can lead to sustained service unavailability.
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed as of version 2.6.7
Frequently Asked Questions
- What is CVE-2026-45802? CVE-2026-45802 is a medium-severity uncontrolled resource consumption vulnerability in setasign/fpdi (composer), affecting versions < 2.6.7. It is fixed in 2.6.7. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- Which versions of setasign/fpdi are affected by CVE-2026-45802? setasign/fpdi (composer) versions < 2.6.7 is affected.
- Is there a fix for CVE-2026-45802? Yes. CVE-2026-45802 is fixed in 2.6.7. Upgrade to this version or later.
- Is CVE-2026-45802 exploitable, and should I be worried? Whether CVE-2026-45802 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-45802 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-45802? Upgrade
setasign/fpdito 2.6.7 or later.