CVE-2026-114609VulnerabilityPublished 27 Oct 2026

Pdfly: fpdf2 implicitly loads external URLs and local image paths when rendering attacker-controlled content

Affects pdflySource GCVE Database

Authoritative record:CVE-2026-114609· Medium 5.8

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

Data as of 27 Oct 2026, 23:14 UTC

CVSS 3.1 base score

5.8Medium

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:N/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade pdfly to 0.5.1_25.

Affected software

Product	Affected	Fixed in
Homebrewpdfly`pkg:brew/pdfly`Other threats	Affected >=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 version 0.5.1_25 that fixes this issue. Applications should upgrade to this version. Additionally, to mitigate risk, applications should avoid rendering untrusted HTML, SVG, or template content, reject user-controlled image source or href values, implement allowlists for resource references, or convert user-supplied images to trusted in-memory objects before passing them to fpdf2.

Description

The pdfly library (fpdf2) implicitly dereferences image resource references when rendering content, which can lead to outbound HTTP(S) requests or local file access attempts if untrusted input is processed. This affects applications that render untrusted HTML, SVG, or image paths without sanitization. The issue can enable Server-Side Request Forgery (SSRF) and limited local file access depending on the image parsing success. A fix is available in version 0.5.1_25.

Impact

Applications rendering untrusted or partially trusted content with pdfly (fpdf2) may be vulnerable to SSRF through outbound HTTP(S) requests to attacker-specified URLs embedded in image references. Additionally, limited local file access attempts may occur if attacker-controlled paths are used, potentially exposing local files if they are valid image or SVG resources. The severity depends on the application's handling of untrusted input controlling resource references.

Summary

fpdf2 uses a shared internal image-loading mechanism that automatically fetches HTTP(S) URLs and opens local filesystem paths when rendering images embedded in HTML, SVG, or templates. If an application passes untrusted content to APIs like FPDF.image() or FPDF.write_html(), this can cause SSRF by making outbound requests to attacker-controlled destinations or attempts to open local files. The local file access impact is limited to files recognized as valid images or SVGs by fpdf2. This vulnerability affects versions >=0.4.0 and <0.5.1_25 and is fixed in 0.5.1_25.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 23:14 UTC

Technical details

References

Community reviews

Related threats