Craft CMS versions from 4.0.0-RC1 before 4.18.2 and from 5.0.0-RC1 before 5.10.6 contain an authenticated remote code execution vulnerability in control panel element-search condition handling. A JSON cleanse bypass in condition.config allows Yii behavior/event configuration keys to be interpreted after decoding, enabling command execution as the PHP/web user.
CVE-2026-78416
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 40% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 60%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 24, 20265.10.6
Patch available: craftcms/cms 5.10.6
https://github.com/craftcms/cms/releases/tag/5.10.6Authenticated RCE via `condition.config` JSON cleanse bypass | Hackrate
https://www.hckrt.com/hacktivity/HCKRT-JD662PVendor Advisories for CVE-2026-78416(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 17:05 UTCEG score recompute
- 2026-08-25 17:05 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 04:23 UTCEG score recompute
- 2026-08-25 04:23 UTCGHSA enrichment
- 2026-08-25 04:10 UTCEG score recompute
- 2026-08-25 04:10 UTCGHSA enrichment
- 2026-08-24 16:25 UTCEG score recompute
- 2026-08-24 16:08 UTCEG score recompute
- 2026-08-24 15:46 UTCEG score recompute
- 2026-08-24 15:46 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-78416?
When was CVE-2026-78416 disclosed?
Is CVE-2026-78416 actively exploited?
What is the CVSS score of CVE-2026-78416?
How do I remediate CVE-2026-78416?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78416
Is Your Infrastructure Affected by CVE-2026-78416?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.