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.
The team recommends blocking the installer even after updating. htaccess rule, or removing the file and keeping it removed with Composer scripts.
Source link







