setasign/fpdi vulnerabilities

FPDI is a collection of PHP classes facilitating developers to read pages from existing PDF documents and use them as templates in FPDF. Because it is also possible to use FPDI with TCPDF, there are no fixed dependencies defined. Please see suggestions for packages which evaluates the dependencies automatically.

Registry
Composer
Latest
2.6.10
License
MIT

2 known advisories

The latest version, 2.6.10, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require setasign/fpdi:^2.6.10

Is your project on an affected setasign/fpdi?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for setasign/fpdi

  • MediumCVE-2026-45802GHSA-2mgw-7q6p-8grg19 May 2026

    FPDI: Memory Exhaustion and Endless Loop in FPDI leads to Denial of Service

    Affected
    <2.6.7
    Fixed in
    2.6.7
  • MediumCVE-2025-54869GHSA-jxhh-4648-vpp35 Aug 2025

    FPDI allows Memory Exhaustion (OOM) in PDF Parser which leads to Denial of Service

    Affected
    <2.6.4
    Fixed in
    2.6.4

Is your setasign/fpdi version vulnerable?

Which of your client projects still run an old setasign/fpdi?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.