Skip to content
ERP

CVE-2026-55242

8.8
High
EPSS 0.20%Patch availableJul 16, 2026

Authenticated user can trigger server-side template injection to expose unauthorized data.

common questions

Is CVE-2026-55242 being exploited?

Not confirmed. CVE-2026-55242 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.

How severe is CVE-2026-55242?

CVE-2026-55242 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-55242?

Yes. A fix has been recorded for CVE-2026-55242. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55242 affect?

CVE-2026-55242 affects ERPNext versions prior to 15.111.0, ERPNext versions prior to 16.22.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55242?

Upgrade to ERPNext 15.111.0 or 16.22.0; review user roles and template configs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ERPNext versions prior to 15.111.0ERPNext versions prior to 16.22.0
impact

Authenticated standard users can perform server-side template injection to read data beyond permissions; may enable RCE or sensitive data exfiltration.

action required

Immediate action required

affected versions
frappe erpnext
  • affected< 15.111.0
  • affected>= 16.0.0 and < 16.22.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free