KEVWire

Security intelligence, with context.

Response snapshot Oct 27, 2026, 16:01 UTC

Back to the wire
Permalink
VulnerabilityCVE-2026-114609

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

`fpdf2` implicitly dereferences image resource references supplied to rendering APIs. If an application passes untrusted HTML, SVG, template data, or image paths into those APIs, `fpdf2` may issue outbound HTTP(S) requests or attempt to open local filesystem paths.

At a glance

Exploited
Not known
Severity
5.8 Medium (CVSS 3.1)
Chance of exploitation
Not estimated
Sources
1 source

What to do

GitHub lists first patched versions: fpdf2: 2.8.8. Confirm the affected range and upgrade guidance in the exact advisory.

Read GitHub-reviewed advisory GHSA-rw7v-4hrq-x6r9 (opens a new tab)

What happened

## Summary

`fpdf2` implicitly dereferences image resource references supplied to rendering APIs. If an application passes untrusted HTML, SVG, template data, or image paths into those APIs, `fpdf2` may issue outbound HTTP(S) requests or attempt to open local filesystem paths.

This behavior is relevant in applications that render untrusted or user-provided input without sanitizing or restricting embedded resource references.

## Description

Continue reading

In affected versions, `fpdf2` uses a shared internal image-loading mechanism for multiple features. This loader:

* fetches `http://` and `https://` URLs over the network * opens other string values as local filesystem paths

During document processing, resource references embedded in input content are automatically dereferenced using this mechanism.

This behavior is reachable through:

* `FPDF.image()` * `FPDF.write_html()` via HTML ` ` * `FPDF.image()` when rendering SVG files containing ` ` or `xlink:href="...">` * template image elements that forward values into `FPDF.image()`

If an application renders attacker-controlled input through these APIs, that input can cause:

* outbound HTTP(S) requests to attacker-chosen destinations * local file open attempts for attacker-chosen paths

This may enable Server-Side Request Forgery (SSRF) in applications that render untrusted content.

Local file access impact is limited: the library attempts to open the referenced path, but successful embedding depends on the target being a valid and supported image or SVG resource.

`file://` URLs are not specially handled; raw filesystem paths such as `/path/to/file` or `../../file.png` are the relevant local-path cases.

## Impact

This issue affects applications that render untrusted or partially trusted content using `fpdf2`.

Applications may be impacted if they:

* pass untrusted HTML into `write_html()` * render untrusted SVG with embedded ` ` references * pass user-controlled strings into `image()` * allow untrusted template definitions or template field values to control image paths

Potential impacts include:

* outbound requests to internal or external network services * limited local file access attempts depending on file type and parsing success (limited to content that fpdf2 recognizes as a supported image or SVG resource)

The severity depends on how `fpdf2` is integrated and whether untrusted input is allowed to control resource references.

**Example scenarios**

HTML: ```python pdf.write_html(' ') ```

SVG: ```xml

```

Direct image path: ```python pdf.image("../../.env") ```

**Workarounds**

Applications can mitigate this by:

- not rendering untrusted HTML, SVG, or template content - rejecting user-controlled `src` / `href` / image-path values - mapping resources through an application-defined allowlist - converting user-supplied images to trusted in-memory objects before passing them to `fpdf2`

**Credits**

- @kule500 for identifying SSRF via HTML handling - @BudongJW for identifying SVG resource loading as an additional vector - @redyank for analysis of the shared image loading mechanism - @manop55555 for identifying a DNS rebinding bypass in the initial REMOTE_PUBLIC implementation

Affected package ranges reported by GitHub: fpdf2: <= 2.8.7

Scores and how they were measured

CVSS base severity

5.8

Version 3.1As of

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Measurement source (opens a new tab)

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

Not available

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-rw7v-4hrq-x6r9 (opens a new tab)

    The public advisory supplies the description, affected package/version ranges, and any listed CVSS metric. GitHub review is not local review.

    Published Checked

  2. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-rw7v-4hrq-x6r9, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, October 27). fpdf2 implicitly loads external URLs and local image paths when rendering attacker-controlled content (CVE-2026-114609). https://kevwire.com/record/CVE-2026-114609

MLA

"fpdf2 implicitly loads external URLs and local image paths when rendering attacker-controlled content (CVE-2026-114609)." KEVWire, 27 Oct. 2026, kevwire.com/record/CVE-2026-114609.

Chicago

KEVWire. "fpdf2 implicitly loads external URLs and local image paths when rendering attacker-controlled content (CVE-2026-114609)." Last modified October 27, 2026. https://kevwire.com/record/CVE-2026-114609.

Evidence summary (plain text)

fpdf2 implicitly loads external URLs and local image paths when rendering attacker-controlled content (Oct 27, 2026).
`fpdf2` implicitly dereferences image resource references supplied to rendering APIs. If an application passes untrusted HTML, SVG, template data, or image paths into those APIs, `fpdf2` may issue outbound HTTP(S) requests or attempt to open local filesystem paths.

This behavior is relevant in applications that render untrusted or user-provided input without sanitizing or restricting embedded resource references.
CVSS 5.8 (version 3.1; evidence as of Oct 27, 2026; https://github.com/advisories/GHSA-rw7v-4hrq-x6r9).
Sources:
GitHub-reviewed advisory GHSA-rw7v-4hrq-x6r9: https://github.com/advisories/GHSA-rw7v-4hrq-x6r9
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc
Record ID: CVE-2026-114609.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.
About this data

This record was ingested from a data source. Retrieved: Oct 27, 2026, 16:00 UTC. Ingestion is not an independent editorial investigation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

A personal reading checklist on this device, not verified remediation.

Record JSON

Your account

Email alerts

Email alerts are not available yet. To follow your stack today, use its RSS feed, which honors your filters, or connect an AI agent through the API.

Suggest an improvement

Ideas, missing sources, corrections, and bugs are all welcome. No account needed. Suggestions are reviewed by a person before anything changes.

Record details

Record detail