High
Drupal · Drupal core · CVE-2026-132165
Drupal core flaw lets visitors without a login try to reinstall a site and take it over
Drupal ships with an installer script, install.php, that stays on the site after set-up. Under specific conditions, someone with no account can use it to attempt to reinstall Drupal, which can lead to the site being taken over or to code running on the server. Drupal's security team rates it critical (18 out of 25 on its own scale), notes that only uncommon configurations are exploitable, and warned that attack code could appear within hours or days of the fix. No attacks have been reported so far.
- Affected
- Drupal core before 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. Drupal 11.2.x and earlier and 10.5.x and earlier no longer get security fixes, and nor do Drupal 8 and 9. Drupal says some attack routes are closed off if the web server cannot write to, or change permissions on, settings.php.
- What to do
- Update to Drupal 11.4.13, 11.3.22 or 10.6.22; sites on an unsupported release should move to one of these. If you cannot update straight away, block access to /core/install.php in the web server configuration or the .htaccess file in the web root, and make sure the web server cannot write to settings.php. Sites behind the paid Drupal Steward firewall are protected against the known routes, but Drupal still recommends updating.General information summarised from the vendor's advisory at the time of writing, not professional advice. Check the vendor's current advisory before acting.
- Why it’s here
- A flaw in Drupal core that needs no login, rated critical by Drupal's own team, in a system used for many business, charity and public-sector websites.
