Skip to content
Web

CVE-2026-71291

8.8
High
EPSS 0.30%Aug 5, 2026

Authenticated RCE via Twig template rendering in Bolt CMS content fields

common questions

Is CVE-2026-71291 being exploited?

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

How severe is CVE-2026-71291?

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

Not known from our data. No patch reference has been recorded for CVE-2026-71291, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-71291 affect?

CVE-2026-71291 affects Bolt CMS (default installs with allow_twig:true), Bolt pages content field. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71291?

Disable allow_twig on content fields or restrict editor write access; apply vendor patch when released.

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

executive summary
technical analysis
affected
Bolt CMS (default installs with allow_twig:true)Bolt pages content field
impact

Authenticated attackers with edit access can execute arbitrary OS commands as the web server user via Twig payloads in content fields.

action required

Immediate action required

affected versions
bolt core
  • affected<= 6.1

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