A Stranger Can Reinstall Your Drupal Site: CVE-2026-132165 and the install.php Takeover
A critical flaw in Drupal's core installer lets an anonymous attacker re-trigger the setup flow on a live site and seize control, no login required. It was found by Anthropic's AI scanner, affects every supported branch, and Drupal warns exploits could come fast. Here's the risk and the fix.
Executive summary. CVE-2026-132165 (Drupal SA-CORE-2026-017) is a critical unauthenticated flaw in Drupal core's installer. An attacker who can reach install.php on a live site can attempt a reinstall, which can lead to site takeover and code execution, with no login. Drupal rates it 18/25 (critical). Fixed releases are Drupal 10.6.22, 11.3.22 and 11.4.13 (18 November 2026); Drupal 8, 9, 10.5.x and 11.2.x are end of life and get no fix. It was discovered by Anthropic's OSS Scanner, and Drupal warns exploits may surface quickly. No confirmed in-the-wild exploitation yet, and a PoC is reported. If you can't patch immediately, block install.php and make settings.php read-only — Drupal notes some exploit paths are blocked when the web server can't write settings.php.
What it is
| Field | Detail |
|---|---|
| CVE | CVE-2026-132165 (SA-CORE-2026-017) |
| Product | Drupal core — the installer (install.php) |
| Type | Unauthenticated reinstall → site takeover / RCE |
| Severity | Critical (Drupal 18/25) |
| Affected | core < 10.6.22, 11.0–11.3.x < 11.3.22, 11.4 < 11.4.13 |
| Fixed | 10.6.22 / 11.3.22 / 11.4.13 (18 Nov 2026) |
| EOL (no fix) | Drupal 8, 9, 10.5.x, 11.2.x |
| Found by | Anthropic's OSS Scanner |
How a live site gets reinstalled
Drupal's installer runs at install.php to set up a new site. On a running site it's supposed to be inert, but this flaw lets an unauthenticated request re-trigger the installation flow:
- Attacker reaches
install.phpon your live site. - The installer lets an outsider start a reinstall.
- The attacker controls the configuration the installer writes, pointing it at their own settings and creating an administrator.
- From there: code execution and full site takeover.
Drupal notes an important nuance: some exploit paths are blocked if the web server cannot write to settings.php. That's both a mitigation (below) and a reason to verify your permissions.
Why it's serious despite "no attacks yet"
- Unauthenticated + widely deployed. Drupal runs a large share of government, university and enterprise sites, exactly the high-value, internet-facing targets attackers scan for.
- Fast exploitation risk. Drupal itself warns exploits may surface quickly, and a PoC is reported. Historically ("Drupalgeddon"), Drupal core RCEs get mass-exploited within days of disclosure.
- AI-accelerated discovery. Found by Anthropic's automated scanner, part of 2026's trend of AI surfacing deep bugs quickly, which cuts both ways.
Remediation
Now
- Update Drupal core to 10.6.22, 11.3.22 or 11.4.13 (or later) for your branch.
- End-of-life branches (8, 9, 10.5.x, 11.2.x) get no fix — apply the mitigations below and plan an urgent migration.
If you can't patch immediately
- Block access to
install.phpat the web server / reverse proxy (deny the path, or allow only from an admin IP). - Make
settings.phpread-only to the web server user — Drupal says this blocks some exploit paths. - Treat these as risk reducers, not fixes: patch as soon as you can.
Detection and hunting
| Where | Look for |
|---|---|
| Web/access logs | Requests to /core/install.php or install.php from unexpected sources, especially POSTs |
| Filesystem | Recent changes to settings.php, new/modified files in the web root, unexpected modules |
| App | New administrator accounts, changed site config, unfamiliar roles |
| Process | The web/PHP process spawning shells or writing new PHP files |
Conclusion
CVE-2026-132165 is a dangerous combination: unauthenticated, in Drupal core, on internet-facing sites, with a vendor warning that exploitation may come fast. The fix is available for supported branches, and a specific, effective stopgap exists (block install.php, lock settings.php). Patch before the PoC becomes a mass-exploitation wave.
Do this now: update Drupal core to 10.6.22 / 11.3.22 / 11.4.13; if you can't patch this minute, block install.php and make settings.php read-only, then watch your logs for installer requests.
Related: Apache Roller unauthenticated RCE and The Collapsing Patch Window on AI-found bugs.
Sources: BleepingComputer, Horizon3, Techzine, Cyber Kendra, Techgenyz. Confirm exact version ranges against Drupal's SA-CORE-2026-017.
Related research
Java4Shell (CVE-2026-114938): A Base64 Bug in the JVM That Reaches Jira, Jenkins and Keycloak
A memory-corruption bug in the JVM's accelerated Base64 decoder means any Java application that decodes attacker-controlled Base64 (which is nearly all of them) could be exploitable, with researchers demonstrating pre-auth RCE against Jira, Jenkins, Keycloak and others. Here's the blast radius and how to triage it.
OptimJack: How One Compromised A/B-Testing Platform Served Malware From CNN, BBC and HSBC
For about a day, visitors to some of the world's biggest websites were served crypto-stealing, card-skimming malware, loaded from Optimizely's own trusted CDN. One flaw in an A/B-testing vendor put 178 organisations at risk at once. A full analysis of the attack, why it is so hard to spot, and the controls that stop it.
1.09 Million Card Numbers, Kept Too Long: The MUJI Breach and the Cost of Data You Forgot to Delete
MUJI's card operator may have exposed the full card numbers of 1.09 million members, around 345,000 of them still valid, for data gathered up to 2021 and never purged. One report says the numbers sat unencrypted. It is a breach of data that should not have existed. The retention, encryption and PCI lessons every organisation should take.