← All updates

Security / News explained

Drupal’s installer fix comes with a compatibility check

Drupal’s November 18 core updates close an installer attack path and a separate gadget chain. The release notes also flag a theme-registry regression that needs a focused compatibility review.

By Zyel · Published · 5 min read

Drupal’s November 18, 2026 security updates deserve prompt attention. The Security Team has updated its installer advisory with a report of exploitation on live sites as early as November 19 at 19:00 UTC. Under specific conditions, CVE-2026-132165 can allow site takeover or remote code execution. That is a vendor-reported development, without establishing the condition of any particular site. [1]

The same security release also addresses a separate gadget chain, CVE-2026-132166. Its prerequisites are different: another vulnerability must allow unsafe input to reach PHP’s unserialize function. Drupal explicitly says that the gadget chain is not directly exploitable on its own. Keeping those two descriptions separate makes the update easier to assess accurately. [2]

Retire the installation surface deliberately

Drupal includes install.php to set up a site. The installer advisory describes an attacker attempting to reinstall Drupal under certain conditions. It also says that preventing the web server from writing to, or changing permissions on, settings.php mitigates some attack paths. That permission boundary provides only partial mitigation for this advisory. [1]

The wider lesson is about administrative surfaces that outlive their original purpose. An installation screen may be used briefly, then forgotten while the site becomes a long-running service. Its continued availability deserves an explicit decision. The installer should be allowed to finish its shift, rather than remain an unexpected permanent member of the operations team.

Drupal’s installer-hardening documentation, updated November 21, recommends blocking access after installation. It distinguishes installation from the separate update.php script and warns against broad rules that accidentally block updates. It also explains why controls placed in web-server configuration can survive core updates, while manually changed scaffold files or removed files need maintenance through the deployment process. [6]

Our interpretation is that a temporary installer restriction needs an owner and a lifecycle. A team adding a new multisite installation may need a controlled exception; its existing sites still need their normal update path. The useful operating decision is to make that exception deliberate and verify that routine deployments preserve the intended restriction.

Choose the fix for the branch actually running

The November release guidance maps supported branches to specific fixes: Drupal 11.4.x to 11.4.13, Drupal 11.3.x to 11.3.22, and Drupal 10.6.x to 10.6.22. The 11.3.22 notes identify 11.2.x and earlier, plus 10.5.x and earlier, as outside current security coverage. [4]

For the Drupal 10 branch, the 10.6.22 notes identify that release as the security update and describe coverage ending in December 2026 when Drupal 11.5.0 is released. That makes the immediate patch decision part of a larger support-lifecycle conversation. A maintained branch is an ongoing responsibility, rather than a property acquired forever at installation. [5]

For a hypothetical organization with several Drupal sites, the visible brand or theme tells the operator little about which branch each deployment uses. The practical distinction is the installed core version and its dependency state. Treating every site as the same package can turn a straightforward security decision into an avoidable inventory puzzle.

The 11.4.13 release also changes new installations. Previously, the installer attempted to repair settings.php permissions when the file was not writable. It now reports an error instead. The release notes say this change affects new installations and does not affect existing sites. An installation failure after the update therefore deserves attention to the documented permission requirement. [3]

The compatibility issue is documented too

The release notes flag a theme-registry regression affecting some contributed and custom code, including Search API. They describe missing theme-hook errors and identify 11.4.14 as the planned fix. That is a known compatibility concern in the release documentation; it should be included in the deployment conversation alongside the security fixes. [3]

For sites on 10.6.22 or 11.3.22 that encounter this regression, the release notes recommend moving to Drupal 11.4 so they can adopt 11.4.14 when it becomes available. This is a branch-migration recommendation in the published notes, rather than a claim that the planned follow-up release has already shipped. [5]

The linked issue explains the mechanism: code rendering late in a request can encounter a runtime theme registry that has already been emptied. Its Search API example concerns post-request indexing of rendered HTML. The report identifies 10.6.22 and 11.3.22, and also 11.4.0 through 11.4.13, so the underlying behavior should not be described as newly introduced across every branch on November 18. [7]

Imagine a hypothetical publisher whose pages appear normal while search indexing depends on rendered content. A homepage check would be a narrow acceptance test for that workflow. Content edits, the relevant rendering path and search output would provide a more useful picture of whether the documented regression matters to that application. This is an illustrative operating example, not a report of a tested site.

The documented regression calls for focused verification and a supported remediation plan. The installer’s reported exploitation adds urgency to the security update. An unexpected rendering error needs investigation while the site’s access restrictions and corrected software remain part of that investigation. [1]

Keep the two vulnerability claims distinct

The gadget-chain advisory describes methods that can become an execution path when another flaw supplies unsafe deserialization. It does not claim that every Drupal installation already has that separate vulnerability. Its fix belongs in the same maintenance decision, while the application’s handling of untrusted serialized data remains a separate engineering concern. [2]

A useful update record connects the vendor’s guidance with the version actually deployed and the workflows actually checked. Record the chosen release, the installer’s intended availability and the relevant compatibility result. That gives the next operator a clear account of the change while keeping facts about a specific site separate from what a public advisory establishes.

Sources + further reading

Source dates describe the original material. Publication above is the date this Zyel article went live.

  1. Drupal core installer advisory SA-CORE-2026-017Drupal · Checked Nov 21, 2026
  2. Drupal core gadget-chain advisory SA-CORE-2026-018Drupal · Checked Nov 21, 2026
  3. Drupal 11.4.13 security release notesDrupal · Checked Nov 21, 2026
  4. Drupal 11.3.22 security release notesDrupal · Checked Nov 21, 2026
  5. Drupal 10.6.22 security release notesDrupal · Checked Nov 21, 2026
  6. Securing the Drupal installerDrupal · Checked Nov 21, 2026
  7. Theme-registry regression report, issue 3639497Drupal · Checked Nov 21, 2026

Reader discussion

What would you ask next?

Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.

No reader comments yet.

10–2,000 characters. Plain text. Leave out passwords, private project data and personal contact details. A blank display name appears as Anonymous.

Complete the CAPTCHA before sending. Verification runs on your device.