Craft CMS up to 4.17.11/5.9.17 Component::cleanseConfig signal handler

Summaryinfo

A vulnerability was found in Craft CMS up to 4.17.11/5.9.17. It has been rated as problematic. This vulnerability affects the function Component::cleanseConfig. The manipulation leads to signal handler. This vulnerability is uniquely identified as CVE-2026-44011. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Craft CMS up to 4.17.11/5.9.17. This issue affects the function Component::cleanseConfig. The manipulation with an unknown input leads to a signal handler vulnerability. Using CWE to declare the problem leads to CWE-479. The product defines a signal handler that calls a non-reentrant function. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Craft CMS is a content management system (CMS). From 4.0.0 to before 4.17.12 and 5.9.18, Craft CMS which contains an input-handling flaw in a Yii object creation path that let any authenticated user inject malicious configuration and execute arbitrary commands on the server. The request-controlled condition field layouts data is converted into a live FieldLayout object without a Component::cleanseConfig() boundary. Because Craft configures models before parent::__construct(), attacker-controlled special config keys can take effect during object creation, and FieldLayout initialization then triggers a same-request event. This vulnerability is fixed in 4.17.12 and 5.9.18.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-44011 since 05/04/2026. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are required for exploitation. Technical details are known, but no exploit is available.

Upgrading to version 4.17.12 or 5.9.18 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Craft

Name

• CMS

Version

• 4.17.0
• 4.17.1
• 4.17.2
• 4.17.3
• 4.17.4
• 4.17.5
• 4.17.6
• 4.17.7
• 4.17.8
• 4.17.9
• 4.17.10
• 4.17.11
• 5.9.0
• 5.9.1
• 5.9.2
• 5.9.3
• 5.9.4
• 5.9.5
• 5.9.6
• 5.9.7
• 5.9.8
• 5.9.9
• 5.9.10
• 5.9.11
• 5.9.12
• 5.9.13
• 5.9.14
• 5.9.15
• 5.9.16
• 5.9.17

License

• free

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion