Drupal's installer was designed to run once. CVE-2026-132165 is what happens when it stays open.
An unauthenticated attacker reaches install.php, bypasses the already-installed check, restarts the installation with their own database credentials, and overwrites settings.php. From there it's full administrative access — and from there, code execution is just using the tools Drupal already provides.
Fixed in Drupal 11.4.13. The Drupal security team warns exploits may surface quickly.
The two CVEs
- CVE-2026-132165 (SA-CORE-2026-017) — anonymous RCE via installer. This is the emergency.
- CVE-2026-132166 (SA-CORE-2026-018) — gadget chain, requires an authenticated admin. Patched in the same release. Close it in the same update.
If you can't patch right now
Two controls, both required:
-
Block
install.phpat the web server (Apache:Deny from all; nginx:deny alllocation block) -
Make
settings.phpread-only —chmod 444so the web server user can't overwrite it
These reduce the attack surface. They are not a fix. Schedule the update within hours.
EOL branches get nothing
Drupal 8, 9, 10.5.x, and 11.2.x are end-of-life. No patch is coming. Apply interim mitigation and treat the branch migration as urgent.
After patching
Check web server logs for any requests to install.php since deployment. Check the modification time on settings.php — if it changed after go-live, treat it as evidence of exploitation. Look for new admin accounts and unexpected PHP files in the files directory.
Full breakdown with patch commands, hunt queries, and FAQ: https://threataft.com/articles/cve-2026-132165-drupal-installer-rce
Top comments (0)