On this page (7 sections)
On 2026-11-18 the Drupal Security Team published SA-CORE-2026-018, an advisory for a gadget chain in Drupal core, tracked as CVE-2026-132166. The advisory rates it Moderately critical and says the issue is not directly exploitable on its own.
The practical risk is what it adds to another bug. If a site (core, a contributed module or custom code) ever passes attacker-controlled data to PHP's unserialize(), this chain of methods could help an attacker reach remote code execution. Anyone running a supported Drupal 10 or 11 release should plan the update; sites on end-of-life versions have a bigger problem than this one advisory.
What the advisory says
Drupal describes the problem as a chain of methods in core that could become exploitable when an insecure deserialization vulnerability exists on the site. It states the chain presents no direct threat, and that exploitation requires a separate vulnerability that lets an attacker pass unsafe input to unserialize().
The advisory's risk string is AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:Uncommon. Read plainly, that means complex attack conditions, administrator-level access in the scoring model, full confidentiality and integrity impact if it works, theoretical exploit maturity, and an uncommon target distribution. The advisory was reported by Drew Webber (mcdruid) of the Drupal Security Team and fixed by several Security Team members.
Why a gadget chain matters
PHP's unserialize() rebuilds objects from a string. If an attacker controls that string, they can make PHP create objects of classes already loaded in the application. Some classes run code automatically when they are created, used or destroyed. A gadget chain links several such classes so that a harmless-looking object ends up triggering something dangerous, such as running code.
The gadget chain is not the entry point. It is the second half of an attack. Without a way to feed untrusted data into unserialize(), the chain does nothing. Removing known chains from core is defense in depth: it shrinks what an attacker can do if a deserialization bug appears elsewhere, for example in a contributed module or custom code.
Who is affected
Per the advisory, these core versions are affected: anything below 10.6.22, 11.0.0 up to but not including 11.3.22, and 11.4.0 up to but not including 11.4.13. The advisory does not claim a site is exploitable merely by running these versions. The higher-risk sites are those that also have a deserialization weakness somewhere in their code.
| If you run | Update to | Status |
|---|---|---|
| Drupal 11.4.x | 11.4.13 | Supported |
| Drupal 11.3.x | 11.3.22 | Supported |
| Drupal 11.2.x and below | No fix offered | End-of-life, no security coverage |
| Drupal 10.6.x | 10.6.22 | Supported |
| Drupal 10.5.x and below | No fix offered | End-of-life, no security coverage |
| Drupal 8 and 9 | No fix offered | End-of-life |
If you are on an end-of-life branch, the advisory offers no patch for you. The fix is to upgrade to a supported branch, not to wait for a backport.
How to check your exposure
Start with your installed core version. If you manage Drupal with Composer, this read-only command lists the installed core package version; run it from the project root and compare the result with the fixed versions above.
composer show drupal/coreIf you use Drush, this prints the Drupal version of the site you run it against.
drush statusYou can also read the version in the admin interface under Reports, Status report. Then ask a second question: does any custom or contributed code call unserialize() on data that can come from users, requests, cookies, uploaded files or external services? This read-only search lists calls in your custom code; adjust the paths to your layout and review each hit by hand.
grep -rn "unserialize(" web/modules/custom web/themes/customWhat to do now
- Identify every Drupal site you run, including staging, old microsites and sites managed by agencies.
- Check each site's core version with composer show drupal/core, drush status or the Status report.
- Take a database and files backup, and test the update on staging first.
- Update to 11.4.13, 11.3.22 or 10.6.22, whichever matches your branch.
- If you are on 11.2.x or below, 10.5.x or below, 8 or 9, plan an upgrade to a supported branch; these receive no security coverage.
- Audit custom code and contributed modules for unserialize() calls on untrusted input and fix or remove them.
- After updating, clear caches and confirm the new version in the Status report.
For a Composer-managed site, the update looks like this. It updates core packages to the newest release your version constraints allow, runs database updates and rebuilds caches. Check the result against the fixed version for your branch.
composer update "drupal/core-*" --with-all-dependencies
drush updatedb -y
drush cache:rebuildYour project may pin core through drupal/core-recommended or a different constraint, so check composer.json to make sure the constraint allows the fixed version. Afterwards, re-run composer show drupal/core to confirm the result.
Detection and monitoring
The advisory does not describe indicators of compromise, and it reports no known exploitation, so there is nothing specific to hunt for in logs. Sensible general monitoring still applies: watch for unexpected PHP files appearing in writable directories, new administrator accounts, and unusual POST requests carrying long encoded or serialized-looking values to pages that should not accept them.
A web application firewall can add a filtering layer in front of a site, but it is not a substitute for updating core; see what a WAF is and is not. To keep an inventory of what your sites are running, an outside-in security scan can help, and the security guides hub covers general hardening. If you suspect a site was already compromised, follow what to do when a website is hacked.
Timeline
- 2026-11-18: Drupal publishes SA-CORE-2026-018 with fixed releases 10.6.22, 11.3.22 and 11.4.13.
- As of this writing: no NVD record for CVE-2026-132166, and no exploitation reported in the advisory.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
