Threat intel5 min read
Drupal fixes critical installer flaw that allows site takeover
A bug in Drupal core's install.php lets an attacker with no account try to reinstall a live site, leading to takeover or code execution. Update to 11.4.13, 11.3.22 or 10.6.22 and block the installer.
4Tify Team

Drupal shipped security releases on 18 November 2026 for a critical flaw in the core installer. Under the right conditions, an attacker with no account on the site can use install.php to try to reinstall Drupal over a live site, which can end in a full takeover or remote code execution. The fixed versions are 11.4.13, 11.3.22 and 10.6.22.
What happened
The Drupal Security Team published two core advisories on the same day. The serious one is SA-CORE-2026-017 (CVE-2026-132165), rated Critical at 18 out of 25 on Drupal's own risk scale. The second, SA-CORE-2026-018 (CVE-2026-132166), is rated Moderately critical at 14 out of 25. Both are fixed by the same releases.
There are no reports of either bug being used in attacks so far, and neither CVE is in the CISA Known Exploited Vulnerabilities catalog. Drupal's score for the installer flaw does record that a proof of concept exists, so the safe assumption is that working exploits will follow.
Who is affected
Every supported Drupal 10 and 11 branch before the fix:
- Drupal 11.4.x before 11.4.13
- Drupal 11.3.x before 11.3.22
- Drupal 10.6.x before 10.6.22
Sites on Drupal 11.2.x or older, 10.5.x or older, and Drupal 8 or 9 get no patch at all. Those branches are end of life, so the only fix is to move to a supported release.
How the installer flaw works
Drupal ships install.php to set up new sites. Once a site is running, that script should have nothing left to do. The bug lets an attacker reach the installer on an existing site and, under specific conditions, push it into a reinstall. Whoever completes that reinstall controls the site, and from there can run their own code on the server.
Drupal rates the attack as complex and the vulnerable setup as uncommon, but no login is needed. Some attack paths fail if the web server cannot write to settings.php or change its permissions. Drupal is clear that this only blocks some paths and does not replace the update.
The release also changes how new installs behave. If settings.php is not writable during setup, the installer now stops with an error instead of trying to change the file's permissions itself. Existing sites are not affected by that change.
The gadget chain
CVE-2026-132166 is a different kind of problem. Drupal core contains a chain of methods that an attacker could abuse for code execution, but only if the site has a second, separate bug that passes untrusted input to PHP's unserialize(). On its own it cannot be exploited. It is still worth closing, since custom code and contributed modules are where deserialization bugs tend to appear.
What to do now
- Update. Move to 11.4.13, 11.3.22 or 10.6.22 depending on your branch. The details are in Drupal's advisory SA-CORE-2026-017.
- Check the version you are actually running. Open the status report at
/admin/reports/statusand confirm the new version number after deploying, especially on staging copies and forgotten microsites. - Block the installer. Drupal recommends this for every installed site. On Apache, deny
/core/install.phpin the virtual host. On Nginx, use a prefix match such aslocation ^~ /core/install.php { return 404; }. Then runcurl -I and expect a 403 or 404. Keepupdate.php` reachable for admins. The steps are in Drupal's guide to securing the installer. - Lock down
settings.php. Make sure the web server user cannot write to it or change its permissions. - Plan the upgrade if you are on an old branch. Sites on 11.2.x, 10.5.x, Drupal 8 or 9 stay exposed until they move.
One known issue: the new releases include a theme registry regression that breaks some contributed and custom code, the Search API module among them, with errors such as "Theme hook field not found". Drupal plans the fix for 11.4.14. Test before you deploy, but do not let it hold back the security update on sites where it does not apply.
How we can help
A reachable install.php and an unpatched core version are both visible from outside the site. Our vulnerability scanning service checks public web applications for outdated CMS versions and exposed setup and admin scripts, so cases like this show up on a report before someone else finds them.