Skip to main content
VulnerabilityPublished

CVE-2026-114610: fpdf2 · Exponential SVG '<use>' expansion causes CPU and memory exhaustion in 'FPDF.image()'

Affects pdflySource GCVE Database

0
Authoritative record:CVE-2026-114610· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.5.1_25 when convenient.

Data as of 27 Oct 2026, 23:14 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.5.1_25
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade pdfly to 0.5.1_25.

Affected software

ProductAffectedFixed in
Homebrewpdflypkg:brew/pdflyOther threatsAffected
  • >=0.4.0 <0.5.1_25
Fixed in
  • 0.5.1_25

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in fpdf2 version 0.5.1_25 that fixes this issue. Users should upgrade to this version or later to mitigate the vulnerability. No additional action is required if the patch is applied. Until patched, avoid processing untrusted SVG input with FPDF.image().

Description

fpdf2 contains a vulnerability where nested SVG <use> references cause exponential growth in memory and CPU usage during image processing. This occurs because fpdf2 deep-copies referenced SVG objects recursively, leading to resource exhaustion. A crafted SVG under 1 KB can cause the process to consume excessive memory and CPU, resulting in a MemoryError and denial of service in PDF generation workflows.

References

Community reviews

Loading reviews…