Skip to content
Web

CVE-2026-72781

8.7
High
EPSS 0.54%Patch availableAug 11, 2026

Authenticated RCE in Craft CMS via Twig sandbox allowing server-side code execution

common questions

Is CVE-2026-72781 being exploited?

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

How severe is CVE-2026-72781?

CVE-2026-72781 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-72781?

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

What does CVE-2026-72781 affect?

CVE-2026-72781 affects Craft CMS >=4.0.0-RC1 and <4.18.3, Craft CMS >=5.0.0-RC1 and <5.10.7, Twig sandbox (Craft CMS), yii\base\Component gadget chain. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72781?

Update to 4.18.3 or 5.10.7+, restrict control-panel access, audit admin accounts, rotate creds

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 and <4.18.3Craft CMS >=5.0.0-RC1 and <5.10.7Twig sandbox (Craft CMS)yii\base\Component gadget chain
impact

Authenticated control-panel user can render malicious Twig to execute arbitrary code on server via yii\base\Component gadget.

action required

Immediate action required

affected versions
craftcms cms
  • affected>= 5.0.0-RC1 and < 5.10.7
  • affected>= 4.0.0-RC1 and < 4.18.3
vendor says fixed in5.10.7, 4.18.3

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