# CVE-2026-31017: Server-side request forgery in n/a

> Attackers can exploit insufficient HTML sanitization in PDF generation to force server-side requests to internal services, potentially disclosing sensitive information.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-2vgp-8568-m98f

## What is CVE-2026-31017?

CVE-2026-31017 is a critical server-side request forgery vulnerability in Frappe Erpnext, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) vulnerability exists in the Print Format functionality of ERPNext v16.0.1 and Frappe Framework v16.1.1, where user-supplied HTML is insufficiently sanitized before being rendered into PDF. When generating PDFs from user-controlled HTML content, the application allows the inclusion of HTML elements such as <iframe> that reference external resources. The PDF rendering engine automatically fetches these resources on the server side. An attacker can abuse this behavior to force the server to make arbitrary HTTP requests to internal services, including cloud metadata endpoints, potentially leading to sensitive information disclosure.

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

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

It affects 2 products.


Products: Frappe Erpnext, Frappe Frappe.

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

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

## Is CVE-2026-31017 being exploited?

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

## Other vulnerabilities in Frappe Erpnext

- [CVE-2026-44442](https://insights.sbomify.com/CVE-2026-44442/): ERPNext: Unauthorised Document modification due to missing validation (critical 9.9)
- [CVE-2026-38431](https://insights.sbomify.com/CVE-2026-38431/): Code injection in n/a (critical 9.8)
- [CVE-2025-66438](https://insights.sbomify.com/CVE-2025-66438/): Code injection in n/a (critical 9.8)
- [CVE-2025-66439](https://insights.sbomify.com/CVE-2025-66439/): SQL injection in n/a (critical 9.8)
- [CVE-2025-66440](https://insights.sbomify.com/CVE-2025-66440/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31017 is a critical server-side request forgery vulnerability in Frappe Erpnext, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31017 in the wild and no public exploit code.

Affected product: Frappe Erpnext. 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-31017/ (Markdown: https://insights.sbomify.com/CVE-2026-31017/index.md)
```

## Sources

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

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