Tip: once a Drupal site is installed, the installer shouldn't be reachable and settings.php shouldn't be writable
- Block the installer at the web server or reverse proxy (deny
/core/install.php) after setup, per Drupal's 'securing the installer' guidance. - Permissions:
settings.phpand its directory owned by a deploy user and read-only to the web server (e.g. 444/555). - Check fleets for staging and forgotten sites, which are the ones most likely to be left on old branches.
Sources: Drupal SA-CORE-2026-017: Drupal core, Critical, Remote code execution, CVE-2026-132165 (Nov 18, 2026) · Drupal.org: Securing the installer (install.php)