# CVE-2026-109603: Frappe Framework before 16.17.0 Authenticated SSRF and LFI via pdfkit

> Authenticated attackers can exploit a vulnerable pdfkit library in Frappe Framework to perform server-side request forgery and local file inclusion.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-8q9q-vqwh-rpm8, GHSA-pj59-9hv9-rmrv

## What is CVE-2026-109603?

CVE-2026-109603 is a medium-severity server-side request forgery vulnerability in frappe, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Frappe Framework 15.x before 15.107.3 and 16.x before 16.17.0 relies on a vulnerable pdfkit library (CVE-2025-26240) for PDF generation, enabling server-side request forgery and local file inclusion. Authenticated attackers can supply crafted content to PDF rendering to make the server fetch internal resources or embed local server files in generated PDFs.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-109603?


## How do I fix CVE-2026-109603?

No fix has been published for CVE-2026-109603 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109603 being exploited?

There is no known exploitation of CVE-2026-109603 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109603 and fix it if it is affected.

What it is: CVE-2026-109603 is a medium-severity server-side request forgery vulnerability in frappe, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109603 in the wild and no public exploit code.

Affected product: frappe. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109603/ (Markdown: https://insights.sbomify.com/CVE-2026-109603/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109603
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109603
- OSV: https://osv.dev/vulnerability/CVE-2026-109603

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109603/
Summaries are generated and may contain mistakes; the official description above is the record.