Drupal CVE-2026-132165 Installer Flaw Risks Site Takeover

Drupal has patched a critical flaw in its content management system that could let an attacker with no login credentials use the built-in installer to attempt to reinstall a live website, potentially taking it over or running their own code on the server. The fix shipped on 18 November in Drupal 10.6.22, 11.3.22 and 11.4.13.
How the installer flaw works
Drupal core ships with install.php, the script used to set up a new site, and the file stays on the site after installation. Core's default .htaccess rules do not block requests to it, so blocking it is left to each site. Under specific conditions, an attacker can invoke that installer against an already-installed site and begin a reinstall. The Drupal Security Team rates the flaw critical, 18 out of 25 on its own risk scale, in advisory SA-CORE-2026-017. Exploitation is rated complex, the vulnerable configurations are uncommon, and the advisory records an existing proof-of-concept exploit. No attacks have been reported. Some exploit paths are blocked where the web server cannot write to or change permissions on settings.php, the file that holds database credentials and site configuration.
The flaw was found by Anthropic's OSS Scanner, an automated service the AI company launched on 8 October to look for vulnerabilities in open-source projects that opt in. Findings go to maintainers with a reproducer and, where available, a candidate patch.
Which versions are affected
Every release below 10.6.22 is affected, along with Drupal 11 releases from 11.0.0 before 11.3.22 and from 11.4.0 before 11.4.13. Sites on Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end of life and receive no fix. Those sites must move to a supported branch. The update also fixes CVE-2026-132166, a moderately critical issue in which attackers with admin privileges could gain remote code execution if the application deserializes untrusted data because of another security flaw. The security team had warned site owners in an advance notice earlier in the week to set aside time for the update, saying exploits might be developed within hours or days.
What site owners should do now
Update to the fixed release for your branch: 10.6.22, 11.3.22 or 11.4.13. Then block public access to /core/install.php even after updating, using a deny rule in the web server configuration, an .htaccess rule, or by removing the file and keeping it removed with Composer scripts. Check that the web server cannot write to settings.php. Sites that use the paid Drupal Steward protection service are already protected from known attack vectors, according to the team, but should still update in case other attack vectors are found.
Second critical Drupal flaw in two months
This is the second critical remote code execution flaw fixed in Drupal core in two months, after the Field UI flaw patched on 14 October, which also had at least one exploit path that needed no login. The exposure is wide: in the week of 8 November, 154,485 of the 528,430 sites reporting usage data to drupal.org, about 29 percent, were running end-of-life branches. The 11.3.x branch and Drupal 10 lose security coverage altogether in December. The security team said on 2 November that a surge of security reports, which it attributes to AI tools, is more than it can sustain at its current funding, and it is cutting security coverage for core minor versions from 12 months to 8 starting in 2027.