Drupal Patches Critical Installer Flaw That Could Give Unauthenticated Attackers Control of Sites
Drupal Patches Critical Installer Flaw That Could Give Unauthenticated Attackers Control of Sites
Under specific conditions, a critical vulnerability in Drupal core can allow an attacker without login credentials to use the built-in installer to attempt to reinstall a site.
That can lead to a site takeover or remote code execution, and the project rates the vulnerable configurations as uncommon. Fixed releases for all supported branches shipped yesterday.
The Drupal Security Team disclosed the flaw, tracked as CVE-2026-132165, yesterday and rated it critical, 18 out of 25 on the project’s risk scale.
The installer ships in every copy of Drupal core as the file /core/install.php and 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.
No attacks are reported in the security advisory, which rates exploitation as complex and records an existing proof-of-concept exploit. Some exploit paths are blocked where the web server cannot write to or change permissions on settings.php.
The team had told site owners in an advance notice earlier this week to set aside time for the update, warning that exploits may be developed within hours or days.
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.
What to Do Now
The fixed versions, detailed in the project’s release notes, are:
- Drupal 11.4.x: update to 11.4.13
- Drupal 11.3.x: update to 11.3.22
- Drupal 10.6.x: update to 10.6.22
The team recommends blocking the installer even after updating. Sites that cannot update yet should follow the project’s installer guidance, updated yesterday, which describes three options: a deny rule in the web server configuration, an .htaccess rule, or removing the file and keeping it removed with Composer scripts.
Sites that use the Drupal Steward protection service are already protected from known attack vectors, according to the team, and should still update in case new vectors emerge.
Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end-of-life and get no fix. The 11.3.x branch and Drupal 10 lose security coverage altogether in December under the project’s support schedule.
In the week of November 8, 154,485 of the 528,430 sites reporting usage data to drupal.org, about 29 percent, were running end-of-life branches.
The flaw was found by Anthropic’s OSS Scanner, an automated service the AI company launched on October 8 to look for vulnerabilities in open-source projects that opt in. Findings go to maintainers without human review, each with a reproducer and, where available, a candidate patch, according to its launch announcement.
Drupal’s security team said on November 2 that a surge of security reports, which it attributes to AI tools, is more than it can sustain at its current funding, and that it is cutting security coverage for core minor versions from 12 months to 8 starting in 2027.
This is the second critical remote code execution flaw fixed in Drupal core in two months, after the Field UI flaw patched on October 14, which also had at least one exploit path that needed no login.
