The installer remains part of the attack surface

Drupal's 18 November advisory says CVE-2026-132165 can let an attacker attempt to reinstall a site through install.php under specific conditions. A successful path can lead to site takeover or remote code execution. The affected branches are Drupal 10 releases before 10.6.22 and Drupal 11 releases before 11.3.22 or 11.4.13, according to the vendor's version ranges.

Drupal also issued CVE-2026-132166 for a separate gadget chain. The security team says that chain is not directly exploitable on its own; it requires another insecure deserialization path. Treat it as context for the core update, not a second standalone takeover claim.

File permissions change the exposure

Drupal says some installer exploit paths are mitigated when the web server cannot write to or change permissions on settings.php. That is worth checking, but it does not replace the core update.

Close the installer path and check for changes

  1. 1

    Confirm the installed branch. Find production and forgotten staging sites. Upgrade Drupal 10.6 to 10.6.22, Drupal 11.3 to 11.3.22, or Drupal 11.4 to 11.4.13, as applicable. Older unsupported branches need a supported upgrade plan.

  2. 2

    Secure the installer. Follow Drupal's guidance for protecting install.php after installation and verify the web server cannot alter settings.php in normal operation.

  3. 3

    Review unexpected site changes. Check configuration and administrator-account changes, installation requests and web-server logs around the exposure period. Preserve evidence if the site shows signs of a reinstall attempt.

Do not confuse core with Commerce

Our earlier Drupal Commerce article covered a contributed module and order access. This issue is in Drupal core's installation flow. A site can run one without the other, so track both in the inventory rather than closing this advisory because the Commerce module was already updated.