CVE-2026-132166 json
Drupal core contains a chain of methods that could be exploitable when an insecure deserialization vulnerability exists on the site.
published 6d ago modified 7h ago also DRUPAL-CORE-2026-018
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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()`.
Patch / fix
- packagist drupal/core 10.6.22, 11.3.22, 11.4.13
Is CVE-2026-132166 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | drupal/core | <10.6.22 >=11.0.0, <11.3.22 >=11.4.0, <11.4.13 |
10.6.22 11.3.22 11.4.13 |
Classification
- Technology feeds
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.