Quick answers
- Is CVE-2026-31017 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-31017 being exploited in the wild.
- How severe is CVE-2026-31017?
- Critical severity, with a CVSS score of 9.1, published 8 April 2026.
- Which products and versions are affected?
- Frappe ERPNext 16.0.1.
- Is there a fix for CVE-2026-31017?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-31017 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-31017?
- Check whether you run Frappe ERPNext or Frappe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the Print Format functionality of ERPNext v16.0.1 and Frappe Framework v16.1.1. The root cause is the insufficient sanitization of user-supplied HTML before it is processed by the wkhtmltopdf rendering engine. Although JavaScript is disabled, the engine still processes tags such as <iframe> and <img>, automatically fetching referenced external resources on the server side. A remote attacker can exploit this to force the server to make arbitrary HTTP requests to internal network services or cloud metadata endpoints (e.g., AWS/GCP metadata). This can lead to sensitive information disclosure or internal network enumeration.
Affected products
- Frappe ERPNext 16.0.1
- Frappe Frappe Framework 16.1.1
Timeline
- 2026-01-16: disclosed: Reported to vendor and MITRE
- 2026-04-07: other: CVE assigned
- 2026-04-08: advisory: NVD published date