ERPNext vulnerabilities: known CVEs & security history
Frappe · CRM · 5 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all ERPNext release lines — 5 in total. A CVE here doesn't mean your version is affected — check ERPNext's current status and the safe version to run.
Known ERPNext CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-38431 | critical | 9.8 | 0% | 2026 |
| CVE-2025-67289 | critical | 9.6 | 0% | 2025 |
| CVE-2026-31017 | critical | 9.1 | 0% | 2026 |
| CVE-2026-38432 | medium | 6.1 | 0% | 2026 |
| CVE-2022-28598 | medium | 6.1 | 5% | 2022 |
Is my ERPNext version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your ERPNext version → · Monitor ERPNext for new CVEs →
ERPNext vulnerabilities — frequently asked
How many known vulnerabilities does ERPNext have?
IsItPatched tracks 5 CVEs for ERPNext. 3 are critical-severity and 0 high-severity. These span every release line — what matters is whether the version you run is affected.
Does ERPNext have any actively-exploited vulnerabilities?
None of ERPNext's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe ERPNext vulnerability?
Among tracked issues, CVE-2026-38431 (CRITICAL, CVSS 9.8) ranks highest — a Code injection weakness.
Is ERPNext safe to use?
It depends on the version. The latest supported ERPNext release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: ERPNext security status · ERPNext end-of-life · actively-exploited CVEs. Always verify against Frappe's advisories — see our disclaimer.