# Drupal's critical installer flaw lets anonymous attackers try to reinstall your site. Update to 10.6.22, 11.3.22 or 11.4.13

> Drupal's November 18 advisory SA-CORE-2026-017 (CVE-2026-132165) covers a flaw in core's install.php that can let an attacker who isn't logged in reinstall a live site, which can lead to takeover or code execution. No attacks have been reported, but Drupal warned exploits could follow within hours or days. Update now, or block the installer until you can.

Published Nov 19, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/drupal-cve-2026-132165-installer-rce-update-10-6-22-11-3-22-11-4-13-what-to-do

**Drupal released core updates on November 18 for a critical flaw in its installer.** Tracked as **CVE-2026-132165** (advisory **SA-CORE-2026-017**), the bug is in `install.php`, the setup script Drupal core ships with. Drupal's advisory says that "under specific conditions, an attacker can use the installer to attempt to reinstall Drupal." If that succeeds, the attacker can take over the site or run code on the server. The fixed releases are **Drupal 10.6.22, 11.3.22 and 11.4.13**.

Why this matters: no login is needed. The DropTimes and Techzine both describe the flaw as exploitable by anonymous visitors. Drupal had warned site owners in advance with a public service announcement on November 16, PSA-2026-11-16, and BleepingComputer reports that the warning said exploits "might be developed within hours or days." Drupal has a track record here. Techzine notes that attacks on Drupalgeddon in 2014 began within hours of the patch, and that months after Drupalgeddon 2 in 2018, more than 115,000 vulnerable sites were still online.

## The two advisories

| | SA-CORE-2026-017 | SA-CORE-2026-018 |
|---|---|---|
| CVE | CVE-2026-132165 | CVE-2026-132166 |
| Drupal rating | Critical, 18/25 | Moderately critical, 14/25 |
| What it is | Installer can be used to try to reinstall an existing site | PHP gadget chain |
| Login needed? | No (complex conditions) | Not exploitable on its own; needs a separate bug that passes untrusted data to `unserialize()` |
| Found by | Anthropic's OSS Scanner (ANT-2026-GMRPK0BU) | Drew Webber, Drupal Security Team (per The DropTimes) |

Drupal's risk string for the installer flaw rates attack complexity as "complex" and says a proof of concept exists. It also rates the affected configuration as "uncommon." So not every site is exposed, but Drupal advises against relying on that, and Techzine quotes its warning: "So don't assume your site is safe."

## Am I affected?

According to the advisory, these versions are affected:

- Drupal core **below 10.6.22**
- **11.0.0 up to 11.3.21**
- **11.4.0 up to 11.4.12**

Drupal **11.2.x and earlier** and **10.5.x and earlier** no longer get security fixes, and neither do Drupal 8 or 9. If you run one of those, you need to move to a supported branch. The DropTimes also notes that Drupal 10 as a whole reaches end of life on **December 9, 2026**. The advisory doesn't mention Drupal 7.

As of the reports we read (SecurityOnline, Techzine, The DropTimes), nobody has reported attacks in the wild or published exploit code. The DropTimes cautions that the lack of reports doesn't prove no one has been attacked.

## What to do

1. **Update core** to the release for your branch:
   - 11.4.x → **11.4.13**
   - 11.3.x → **11.3.22**
   - 10.6.x → **10.6.22**

   With Composer, that's typically:

   ```bash
   composer update "drupal/core-*" --with-all-dependencies
   drush updatedb && drush cache:rebuild
   ```

2. **If you can't update today, block the installer.** BleepingComputer and The DropTimes both recommend denying access to `/core/install.php` in your web server config or the web-root `.htaccess`. On Nginx, The DropTimes suggests a prefix match such as `location ^~ /core/install.php`. Then check that `/core/install.php`, the `/install.php` redirect, and paths with extra segments after it all return 403 or 404. **Don't block `update.php`.**
3. **Make `settings.php` read-only for the web server.** The advisory says this blocks *some* exploit paths. Drupal doesn't present it as a full fix.
4. **Watch Composer scaffolding.** The DropTimes notes that scaffolding can overwrite hand-edited `.htaccess` rules unless you manage them through scaffold configuration. Check that your block is still in place after deploys.
5. **Drupal Steward users:** Drupal says these sites are already protected against known attack paths, but should still update.

One behaviour change came with the fix: when `settings.php` isn't writable, the installer now shows an error for new installs instead of fixing permissions automatically. Per The DropTimes, existing sites aren't affected by this.

## What to watch

Given Drupal's own hours-or-days warning, assume scanning is coming. Check access logs for requests to `install.php` from November 18 onward, and treat any successful hit on an existing site as a possible compromise. Drupal flaws do get used: BleepingComputer notes that CVE-2026-9082, an SQL injection bug, was actively exploited in May.


## Sources

1. [Drupal.org — SA-CORE-2026-017: Drupal core, Critical, Remote code execution](https://www.drupal.org/sa-core-2026-017)
2. [Drupal.org — Drupal core security advisories](https://www.drupal.org/security/core)
3. [BleepingComputer — Drupal patches critical RCE flaw, warns exploits may surface quickly](https://www.bleepingcomputer.com/news/security/drupal-patches-critical-rce-flaw-warns-exploits-may-surface-quickly/)
4. [The DropTimes — Drupal fixes critical installer flaw and gadget chain](https://www.thedroptimes.com/74161/drupal-fixes-critical-installer-flaw-and-gadget-chain)
5. [Techzine — Critical Drupal vulnerability allows attackers to take over sites via the installer](https://www.techzine.eu/news/security/145932/critical-drupal-vulnerability-allows-attackers-to-take-over-sites-via-the-installer/)
6. [SecurityOnline — CVE-2026-132165: Drupal remote code execution fixed in 11.4.13](https://securityonline.info/drupal-remote-code-execution-cve-2026-132165/)
