How severe is GHSA-rw7v-4hrq-x6r9?

GHSA-rw7v-4hrq-x6r9 has a CVSS score of 5.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rw7v-4hrq-x6r9?

GHSA-rw7v-4hrq-x6r9 affects the following packages: fpdf2 (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-rw7v-4hrq-x6r9?

Update fpdf2 to 2.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rw7v-4hrq-x6r9 is resolved across your whole dependency graph.

How do I detect GHSA-rw7v-4hrq-x6r9 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fpdf2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rw7v-4hrq-x6r9 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-rw7v-4hrq-x6r9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rw7v-4hrq-x6r9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rw7v-4hrq-x6r9?

GHSA-rw7v-4hrq-x6r9 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rw7v-4hrq-x6r9?

GHSA-rw7v-4hrq-x6r9 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rw7v-4hrq-x6r9 published, and has it been updated?

GHSA-rw7v-4hrq-x6r9 was published on October 27, 2026 and was last updated on October 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

fpdf2 implicitly loads external URLs and local image paths when rendering attacker-controlled contentGHSA-rw7v-4hrq-x6r9

MEDIUMFix: py-pdf/fpdf2#1824

GHSA-rw7v-4hrq-x6r9 is a medium-severity (CVSS 5.8) Server-Side Request Forgery (SSRF) vulnerability in fpdf2. A fix is available for fpdf2 — see the affected versions and patch details below.

Also known asCVE-2026-114609

Published

Oct 27, 2026

Updated

Oct 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rw7v-4hrq-x6r9.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-rw7v-4hrq-x6r9 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 396,966 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐍fpdf2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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

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 <img src="...">
FPDF.image() when rendering SVG files containing <image href="..."> 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 <image> 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:

pdf.write_html('<img src="http://127.0.0.1:8000/internal.png">')

SVG:

<image href="http://169.254.169.254/latest/meta-data/" />

Direct image path:

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 <img> handling
@BudongJW for identifying SVG <image> 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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`fpdf2`	all versions	2.8.8`pip install --upgrade 'fpdf2==2.8.8'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fpdf2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fpdf2 to 2.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rw7v-4hrq-x6r9 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

## 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 In affected versions, `fpdf2` uses a shared internal image-loading mechanism for multiple features. This loader: * fetches `http://` and `https://` URLs