CVE-2026-132166: Composer/drupal/core vulnerability
Drupal core contains a chain of methods that could be exploitable when an insecure deserialization vulnerability exists on the site. This so-called "gadget chain" presents no direct threat, but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.
This issue is not directly exploitable.
This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/drupal/coreto a version that resolves this vulnerability.Fixed in 10.6.22 - Upgrade
Upgrade
composer/drupal/coreto a version that resolves this vulnerability.Fixed in 11.3.22 - Upgrade
Upgrade
composer/drupal/coreto a version that resolves this vulnerability.Fixed in 11.4.13
Event History
Frequently Asked Questions
What additional condition is required for this to be exploitable?
A separate insecure deserialization vulnerability must allow an attacker to supply untrusted data to PHP's unserialize() function. The gadget chain alone does not provide an exploitation path.
Can this issue be exploited directly against a Drupal site?
No. The available information states that it is not directly exploitable and presents no direct threat by itself.
What is the potential impact if a separate deserialization flaw is present?
The gadget chain could be used as a vector to achieve remote code execution when unsafe attacker-controlled input is deserialized.