Drupal Vulnerability Requires Updates and Installer Blocking
A critical Drupal vulnerability can let an attacker without login credentials use the content management system’s built-in installer to attempt to reinstall a site. Under specific conditions, that may lead to a complete site takeover or remote code execution, meaning the attacker can make the server run commands. Drupal rates the affected configurations as uncommon, but fixed releases are available for every supported branch.
The Drupal Security Team disclosed the flaw as CVE-2026-132165 and rated it critical, scoring it 18 out of 25 on the project’s risk scale. The installer is included in every Drupal core installation as /core/install.php and remains on the site after setup. Drupal’s default .htaccess rules, which are web server instructions controlling access to files and folders, do not block requests to that file. Each site therefore has to block it separately.
The security advisory says exploitation is complex and records an existing proof-of-concept exploit, a working demonstration of how the flaw can be abused. No attacks have been reported. Some possible attack paths are blocked when the web server cannot write to settings.php or change that file’s permissions. The team nevertheless warned site owners in an advance notice earlier in the week to make time for the update, saying exploits could be developed within hours or days.
Every Drupal release below 10.6.22 is affected. The vulnerable Drupal 11 versions are releases from 11.0.0 before 11.3.22 and releases from 11.4.0 before 11.4.13. The project’s fixed releases are Drupal 11.4.13 for the 11.4.x branch, Drupal 11.3.22 for 11.3.x, and Drupal 10.6.22 for 10.6.x. Administrators should also block the installer after updating.
The project’s installer guidance, updated alongside the disclosure, gives three ways to do that: add a deny rule to the web server configuration, add a rule to .htaccess, or remove /core/install.php and use Composer scripts to ensure it stays removed. Composer is a tool used to manage PHP software and its dependencies. Sites using the Drupal Steward protection service are already protected against known attack vectors, according to the Drupal Security Team, but the team still advises updating because new attack paths could emerge.
Older branches cannot receive a fix for this vulnerability. Drupal 11.2.x and earlier, Drupal 10.5.x and earlier, and Drupal 8 and 9 are end of life, meaning they no longer receive security updates. The 11.3.x branch and Drupal 10 are scheduled to lose security coverage altogether in December. Usage data reported to drupal.org in the week of November 8 showed that 154,485 of 528,430 reporting sites, about 29 percent, were running end-of-life branches.
Anthropic’s OSS Scanner, an automated service launched by the AI company on October 8 to search for vulnerabilities in open-source projects that opt in, found the flaw. According to the service’s launch announcement, findings go to project maintainers without human review, with a reproducer and, when available, a candidate patch. The Drupal Security Team said on November 2 that a surge in security reports attributed to AI tools was more than its current funding could sustain. It plans to reduce security coverage for core minor versions from 12 months to eight months starting in 2027.
This is the second critical remote code execution flaw fixed in Drupal core in two months. The earlier issue affected Field UI and was patched on October 14. That flaw also had at least one exploitation path that required no login. For teams responsible for Drupal sites, the immediate priorities are applying the correct branch update, blocking the installer, and planning migration from unsupported releases.
For organisations that need broader help with website and infrastructure security, AEU-I provides security-first IT, infrastructure and consulting. That service does not replace the Drupal update or installer controls described here, which must be applied by the site’s administrators.
Drupal site owners should treat unsupported versions as a separate risk because this flaw has no fix for those branches. Moving to a supported release and keeping the installer inaccessible reduces exposure to both the known proof of concept and possible future attack paths.