CVE-2026-71291: CWE-1336 in bolt core
Bolt CMS renders content field values through Twig's full application-level Environment with no SandboxExtension registered anywhere in the codebase. In src/Entity/Field.php, getTwigValue calls shouldBeRenderedAsTwig, which gates rendering only on the field definition's allow_twig flag and a regex checking for , , or ; when true, the raw field value is compiled and rendered via with no sandboxing.
AI Analysis
Technical Summary
Bolt CMS core renders content field values through Twig's full application-level Environment without registering a SandboxExtension, as detailed in src/Entity/Field.php. The getTwigValue function calls shouldBeRenderedAsTwig, which permits rendering based on the allow_twig flag and a regex check for characters such as , , or ;. When these conditions are met, the raw field value is compiled and rendered with no sandboxing, exposing the system to potentially dangerous Twig code execution. This vulnerability is tracked as CVE-2026-71291 and classified under CWE-1336. It has a CVSS 3.1 score of 8.8, indicating high severity with network attack vector, low attack complexity, requiring low privileges, no user interaction, and impacts confidentiality, integrity, and availability.
Potential Impact
Exploitation of this vulnerability could allow an attacker with low privileges to execute arbitrary Twig code within the Bolt CMS environment, potentially leading to full system compromise including data disclosure, modification, or denial of service. The lack of sandboxing in Twig rendering increases the risk of code injection and execution.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to disable the allow_twig flag on content fields where possible to prevent untrusted Twig code execution. Monitor vendor communications for updates regarding patches or official mitigations.
CVE-2026-71291: CWE-1336 in bolt core
Description
Bolt CMS renders content field values through Twig's full application-level Environment with no SandboxExtension registered anywhere in the codebase. In src/Entity/Field.php, getTwigValue calls shouldBeRenderedAsTwig, which gates rendering only on the field definition's allow_twig flag and a regex checking for , , or ; when true, the raw field value is compiled and rendered via with no sandboxing.
CVSS v3.1
Score 8.8high
Affected software
bolt
core
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Bolt CMS core renders content field values through Twig's full application-level Environment without registering a SandboxExtension, as detailed in src/Entity/Field.php. The getTwigValue function calls shouldBeRenderedAsTwig, which permits rendering based on the allow_twig flag and a regex check for characters such as , , or ;. When these conditions are met, the raw field value is compiled and rendered with no sandboxing, exposing the system to potentially dangerous Twig code execution. This vulnerability is tracked as CVE-2026-71291 and classified under CWE-1336. It has a CVSS 3.1 score of 8.8, indicating high severity with network attack vector, low attack complexity, requiring low privileges, no user interaction, and impacts confidentiality, integrity, and availability.
Potential Impact
Exploitation of this vulnerability could allow an attacker with low privileges to execute arbitrary Twig code within the Bolt CMS environment, potentially leading to full system compromise including data disclosure, modification, or denial of service. The lack of sandboxing in Twig rendering increases the risk of code injection and execution.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to disable the allow_twig flag on content fields where possible to prevent untrusted Twig code execution. Monitor vendor communications for updates regarding patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- TuranSec
- Date Reserved
- 2026-08-05T12:37:57.357Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a7336e7bf8831d539ed92fa
Added to database: 08/05/2026, 13:13:11 UTC
Last enriched: 08/12/2026, 14:36:11 UTC
Last updated: 09/17/2026, 22:01:38 UTC
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.