Skip to content
Web

CVE-2026-78416

8.7
High
EPSS 0.61%Patch availableAug 25, 2026

Authenticated RCE in Craft CMS control panel via JSON condition config.

common questions

Is CVE-2026-78416 being exploited?

Not confirmed. CVE-2026-78416 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.61% probability of exploitation in the next 30 days.

How severe is CVE-2026-78416?

CVE-2026-78416 is rated High with a CVSS score of 8.7. 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-78416?

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

What does CVE-2026-78416 affect?

CVE-2026-78416 affects Craft CMS 4.0.0-RC1 before 4.18.2, Craft CMS 5.0.0-RC1 before 5.10.6. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-78416?

Upgrade to Craft CMS 4.18.2 or 5.10.6; restrict control panel access and audit admin activity

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

executive summary
technical analysis
affected
Craft CMS 4.0.0-RC1 before 4.18.2Craft CMS 5.0.0-RC1 before 5.10.6
impact

Authenticated attackers can achieve remote code execution as the PHP/web user by exploiting a JSON cleanse bypass in control panel element-search conditions.

action required

Immediate action required

affected versions
craftcms cms
  • affected>= 4.0.0-RC1 and < 4.18.2
  • affected>= 5.0.0-RC1 and < 5.10.6

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