Home › Vulnerabilities

Pixel & Tonic Craft CMS signed Twig object templates Flaw CVE-2026-124430: Update Now

Published November 9, 2026 · Last updated November 9, 2026

CVE Patch

The short version: CVE-2026-124430 is a high-severity security flaw in Pixel & Tonic Craft CMS signed Twig object templates. The National Vulnerability Database (NVD) published it on November 8, 2026, and the score it lists is 8.8 out of 10. When FraudMeNot checked on November 9, 2026, CISA had not added CVE-2026-124430 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-124430

The record was filed by vulncheck.com. In its own words: "Craft CMS from 5.10.0 before 5.11.2 contains a remote code execution vulnerability that allows non-administrator control panel users to obtain HMAC-signed Twig templates via the app/render-elements endpoint. Attackers can submit the signed templated returnUrl as the login redirect parameter, triggering unsandboxed renderObjectTemplate() evaluation and executing OS commands as the PHP worker."

Why Craft CMS signed Twig object templates admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on vulncheck.com rated CVE-2026-124430 8.8 (High) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Craft CMS signed Twig object templates running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, the address listed on vulncheck.com gives it 8.7 (High, CVSS 4.0).

Affected Craft CMS signed Twig object templates releases

According to the record, these releases are vulnerable:

  • 5.10.0 up to, but not including, 5.11.2

The type of bug behind CVE-2026-124430

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-1336, Improper Neutralization of Special Elements Used in a Template Engine. MITRE describes this class of bug as follows: "The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine."

Vendor remediation for CVE-2026-124430

The vendor advisory remediation for operators of Craft CMS signed Twig object templates, quoted for this page, is: "For CVE-2026-124430, deploy craftcms/cms 5.11.2 or a later supported release containing this correction. The affected Composer-package interval begins at 5.10.0 and excludes 5.11.2. The maintainer identifies a non-administrator control-panel account and successful authentication as prerequisites; this is not anonymous visitor access. Editorial permissions do not authorize operating-system commands. Account restrictions may reduce exposure while maintenance is arranged, but the retrieved advisory supplies no supported interim workaround. Craft signs an attacker-chosen Twig object template with its global security key during element rendering. That authentic signature is reusable outside the purpose for which it was issued: login redirect handling validates it and subsequently evaluates the template through unsandboxed renderObjectTemplate. Native PHP callables become reachable. The flaw concerns application-context separation, not guessing the key or breaking HMAC. Key rotation alone is not identified as a repair. No malicious template, request sequence or reproduction instructions are needed for the operational response. Execution inherits the PHP/web-server worker's privileges. The vendor identifies possible exposure of the Craft security key, database and environment credentials, CMS content and other files readable by that process. Actual permissions constrain reach; neither universal root access, automatic container escape nor compromise of another host is established. These are potential consequences, not a finding that a customer has lost data. Least privilege limits impact without correcting the signature-use boundary. VulnCheck, the address listed on vulncheck.com, supplies the NVD-hosted record's CVSS 3.1 Primary score 8.8 and CVSS 4.0 Secondary score 8.7, both High. Neither value is an independent NVD analyst assessment or the maintainer's numeric rating: the fetched GHSA numeric CVSS field is empty. Different scoring models do not remove the authenticated control-panel prerequisite. The sources reviewed contain no confirmed exploitation-in-the-wild statement. KEV did not identify this CVE in the slot check; catalog absence does not prove that attacks have never occurred. GHSA-qj3q-j7r4-428p was published October 23, 2026, within the October 9 recency window; the assigned CVE appeared in NVD November 8 at approximately 9:18 AM EST. The CVE explicitly references that matching upstream advisory. Database publication dates establish documentation timing, not when the vulnerable code first existed or when any campaign began. Keep unrelated Craft identifiers and their affected intervals separate. The platform owner should identify running package versions and affected instances, replace vulnerable deployments rather than merely record a planned dependency change, and retain version/scope evidence without copying secrets into tickets. Application owners validate legitimate editorial and login workflows after updating. Identity administrators own any temporary control-panel restriction; existing authorized logs can inform security review without exploit traffic. Closing an exception requires verifying the corrected package actually runs. Patch ownership stays with platform operations, compatibility with application teams, and suspicious worker/configuration activity assessment with security operations."

What to do about it

  • Update now: For CVE-2026-124430, deploy craftcms/cms 5.11.2 or a later supported release containing this correction. The affected Composer-package interval begins at 5.10.0 and excludes 5.11.2. The maintainer identifies a non-administrator control-panel account and successful authentication as prerequisites; this is not anonymous visitor access. Editorial permissions do not authorize operating-system commands. Account restrictions may reduce exposure while maintenance is arranged, but the retrieved advisory supplies no supported interim workaround. Craft signs an attacker-chosen Twig object template with its global security key during element rendering. That authentic signature is reusable outside the purpose for which it was issued: login redirect handling validates it and subsequently evaluates the template through unsandboxed renderObjectTemplate. Native PHP callables become reachable. The flaw concerns application-context separation, not guessing the key or breaking HMAC. Key rotation alone is not identified as a repair. No malicious template, request sequence or reproduction instructions are needed for the operational response. Execution inherits the PHP/web-server worker's privileges. The vendor identifies possible exposure of the Craft security key, database and environment credentials, CMS content and other files readable by that process. Actual permissions constrain reach; neither universal root access, automatic container escape nor compromise of another host is established. These are potential consequences, not a finding that a customer has lost data. Least privilege limits impact without correcting the signature-use boundary. VulnCheck, the address listed on vulncheck.com, supplies the NVD-hosted record's CVSS 3.1 Primary score 8.8 and CVSS 4.0 Secondary score 8.7, both High. Neither value is an independent NVD analyst assessment or the maintainer's numeric rating: the fetched GHSA numeric CVSS field is empty. Different scoring models do not remove the authenticated control-panel prerequisite. The sources reviewed contain no confirmed exploitation-in-the-wild statement. KEV did not identify this CVE in the slot check; catalog absence does not prove that attacks have never occurred. GHSA-qj3q-j7r4-428p was published October 23, 2026, within the October 9 recency window; the assigned CVE appeared in NVD November 8 at approximately 9:18 AM EST. The CVE explicitly references that matching upstream advisory. Database publication dates establish documentation timing, not when the vulnerable code first existed or when any campaign began. Keep unrelated Craft identifiers and their affected intervals separate. The platform owner should identify running package versions and affected instances, replace vulnerable deployments rather than merely record a planned dependency change, and retain version/scope evidence without copying secrets into tickets. Application owners validate legitimate editorial and login workflows after updating. Identity administrators own any temporary control-panel restriction; existing authorized logs can inform security review without exploit traffic. Closing an exception requires verifying the corrected package actually runs. Patch ownership stays with platform operations, compatibility with application teams, and suspicious worker/configuration activity assessment with security operations.
  • Who should act: IT teams, managed service providers, and developers who run or ship Craft CMS signed Twig object templates. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Pixel & Tonic (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 8, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-124430. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-124430 record details from CISA and NVD

  • Attack complexity for CVE-2026-124430: low
  • CVE-2026-124430 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-124430: exploitability 2.8, impact 5.9.
  • Who mapped the weakness type: the address listed on vulncheck.com (Primary)
  • References in the NVD record: 2.

Dates to know

  • November 8, 2026: NVD publishes CVE-2026-124430.
  • November 9, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-124430 is not listed.
  • November 8, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.