Protect.Computer
NEWS

Drupal Patches Critical Flaw That Lets Attackers Reinstall Sites

· 2 min read · Got hacked Network safety
Drupal Patches Critical Flaw That Lets Attackers Reinstall Sites

The Drupal Security Team has released fixes for a critical remote code execution flaw in Drupal core, tracked as CVE-2026-132165 (advisory SA-CORE-2026-017, published November 18). Drupal ships an install.php file used to set up a new site. The advisory says that “under specific conditions” an attacker can use it to attempt to reinstall Drupal, which “can lead to a site takeover or remote code execution.” The advisory rates the issue Critical (18/25) and says some exploit paths are blocked if the web server cannot write to or change permissions on settings.php. BleepingComputer adds that anonymous users can exploit the flaw. It was found by Anthropic’s OSS Scanner.

The release follows an advance warning from the Drupal Security Team earlier this week, quoted by BleepingComputer, that exploits “might be developed within hours or days.” Neither the advisory nor BleepingComputer reports any attacks so far. BleepingComputer also says Drupal fixed a second, moderately critical flaw the same day (CVE-2026-132166), a gadget chain that an administrator could use to reach code execution if the application deserializes untrusted data because of some other bug. We did not read that flaw’s own advisory.

How to check if you’re affected

Affected versions, per SA-CORE-2026-017, are Drupal core before 10.6.22, Drupal 11.0.0 up to (not including) 11.3.22, and 11.4.0 up to (not including) 11.4.13. The advisory says Drupal 11.2 and below, Drupal 10.5 and below, and Drupal 8 and 9 are end of life and get no security coverage, so those sites have no fix to install and need to move to a supported release.

To fix it, update to Drupal 11.4.13, 11.3.22 or 10.6.22. If you cannot upgrade right away, the advisory points to Drupal’s guide for securing the installer. Per that guide:

  • If the site is already installed, install.php is not needed, and blocking it removes the risk from future installer bugs.
  • On Apache, add a <Location "/core/install.php"> block with Require all denied to the server or virtual-host configuration, not to .htaccess, because Apache does not allow <Location> there and the whole site would return a 500 error. On Nginx, add location ^~ /core/install.php { return 404; } inside the server block.
  • The guide also lists an .htaccess option for Apache and removing the file, and says to test the rule before relying on it.
  • Blocking the installer does not affect update.php. To add a new site (for example in a multisite setup), the guide says to allow access temporarily or use drush site:install.

The advisory says sites protected by the paid Drupal Steward service are already covered against known attack vectors, but should still upgrade in case additional vectors turn up. If you manage a site you did not set up yourself, asking your host whether it already blocks the installer is our suggestion; the guide notes that some managed hosts do.

Sources

Related earlier coverage: Drupal Patches Critical Field UI Flaw That Can Lead to RCE (a different flaw).

Related reading