News
Drupal patched an installer bug that can reinstall a site with no login.
On uncommon Drupal setups, someone with no account can use the core installer to try to reinstall the site, which can take it over or run code. Supported branches are fixed in 10.6.22, 11.3.22, and 11.4.13.

Impact
- What was impacted
- Drupal core's installer, the file /core/install.php, tracked as CVE-2026-132165. Drupal rates it critical, 18 out of 25 on the project's scale. Under specific conditions an attacker with no login can try to reinstall the site, which can lead to a site takeover or remote code execution. The project calls the vulnerable configurations uncommon and rates exploitation complex. The advisory reports no attacks and records an existing proof of concept. Some of those paths are blocked when the web server cannot write settings.php or change its permissions. Core's default .htaccess rules do not block /core/install.php. Affected releases are everything below 10.6.22, Drupal 11 from 11.0.0 before 11.3.22, and Drupal 11 from 11.4.0 before 11.4.13.
- Who was impacted
- Operators of supported Drupal 10.6, 11.3, and 11.4 sites, including sites that finished installation and left install.php in place. Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end of life and get no fix. The 11.3.x branch and Drupal 10 lose security coverage in December. In the week of 8 November, 154,485 of 528,430 sites reporting usage to drupal.org, about 29 percent, were on end-of-life branches. Sites on the Drupal Steward service are already covered for known attack vectors and are still told to update.
- What you need to do
- Update Drupal 11.4.x to 11.4.13, 11.3.x to 11.3.22, and 10.6.x to 10.6.22. Block the installer after the update. If you cannot update yet, use the project's installer guidance updated on 18 November 2026. It describes three options: a deny rule in the web server configuration, an .htaccess rule, or removing /core/install.php and keeping it removed with Composer scripts. Do not treat a block as a replacement for the update on a branch that has a fix. End-of-life branches have no patch in this release.
The Drupal Security Team disclosed CVE-2026-132165 on 18 November 2026 and rated it critical, 18 out of 25 on the project's risk scale. Under specific conditions, someone with no account can use the built-in installer to try to reinstall the site. That can take the site over or run code. The project calls the vulnerable configurations uncommon and rates exploitation complex. The advisory does not report attacks. It does record an existing proof of concept. Some paths are blocked when the web server cannot write to settings.php or change its permissions.
The installer is /core/install.php. It ships with every copy of Drupal core and remains after installation. Core's default .htaccess rules do not block it, so each site has to do that itself. Earlier in the week the team told owners to reserve time for the update and warned that exploits may show up within hours or days. Fixed releases for the supported branches shipped on 18 November 2026: 11.4.13, 11.3.22, and 10.6.22. Every release below 10.6.22 is affected, as are Drupal 11 releases from 11.0.0 before 11.3.22 and from 11.4.0 before 11.4.13.
Install those updates, then block the installer anyway. Sites that cannot update yet should follow the installer guidance the project refreshed on 18 November 2026. The three options it describes are a deny rule in the web server configuration, an .htaccess rule, or removing the file and keeping it removed with Composer scripts. The report does not print the rule text. Sites that use Drupal Steward are already protected against known attack vectors, the team said, and should still update in case new vectors appear.
Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end of life and receive no fix. The 11.3.x branch and Drupal 10 lose security coverage in December under the project's schedule. In the week of 8 November, 154,485 of the 528,430 sites that report usage to drupal.org, about 29 percent, were on end-of-life branches. Anthropic's OSS Scanner found the flaw. That service launched on 8 October and sends findings to maintainers without human review, each with a reproducer and, where one exists, a candidate patch. On 2 November the Drupal security team said a surge of reports it attributes to AI tools is more than current funding can sustain, and that security coverage for core minor versions will drop from 12 months to 8 months starting in 2027. This is the second critical remote code execution flaw fixed in Drupal core in two months. The earlier one was a Field UI flaw patched on 14 October, which also had at least one path that needed no login. This report does not name a CVE for that earlier flaw.
For your AI agent
Agent instructions — copy paste to Claude
You are helping me respond to CVE-2026-132165 in Drupal core. Under specific conditions, someone with no account can use /core/install.php to try to reinstall the site. That can take the site over or run code. Drupal rates it critical, 18 out of 25 on its scale, calls the vulnerable configurations uncommon, and rates exploitation complex. The advisory reports no attacks and records an existing proof of concept. Do not download, write, or run that proof of concept. Facts from the report: - The installer ships in every copy of Drupal core as /core/install.php and stays after installation. Core's default .htaccess rules do not block it. - Some exploit paths are blocked when the web server cannot write settings.php or change its permissions. Do not treat a read-only settings.php as a complete fix. - Affected: every release below 10.6.22, Drupal 11 from 11.0.0 before 11.3.22, and Drupal 11 from 11.4.0 before 11.4.13. - Fixed: 11.4.x to 11.4.13, 11.3.x to 11.3.22, 10.6.x to 10.6.22. The disclosure, the fixed releases, and an update to the installer guidance are dated 18 November 2026 in this report. - Block the installer even after updating. If you cannot update yet, the project's installer guidance describes three options: a deny rule in the web server configuration, an .htaccess rule, or removing the file and keeping it removed with Composer scripts. This report does not include the rule text. Do not invent a rewrite rule. - Drupal Steward already covers known attack vectors, according to the team. Those sites should still update. - No fix for Drupal 11.2.x and earlier, 10.5.x and earlier, or Drupal 8 and 9. The 11.3.x branch and Drupal 10 lose security coverage in December. - In the week of 8 November 2026, 154,485 of 528,430 sites reporting usage to drupal.org, about 29 percent, were on end-of-life branches. - Found by Anthropic's OSS Scanner. A separate Field UI flaw patched on 14 October 2026 also had at least one path with no login. This report does not name a CVE for that flaw. Do not invent one. Context: - What was impacted: Drupal core sites whose installer is still reachable, on the affected releases. - Who should care: operators of Drupal 10.6, 11.3, and 11.4, and anyone still on an end-of-life major or minor that will not get this patch. - What to do: update the supported branch, then block /core/install.php. Use the project's three documented options only as a bridge if the update is not possible yet. Do this in order. Ask before updating Drupal, editing web-server or .htaccess rules, deleting install.php, or changing Composer scripts. Prefer read-only inventory first. Do not write or run an exploit or a proof of concept. 1. Inventory - Record the Drupal core version. Map 11.4.x below 11.4.13 to 11.4.13, 11.3.x below 11.3.22 to 11.3.22, and 10.6.x below 10.6.22 to 10.6.22. If the version is 11.2.x or earlier, 10.5.x or earlier, or Drupal 8 or 9, say this release has no fix for it. - Check whether /core/install.php is still on disk and whether a request from outside can reach it. Read-only only. - Note whether the web server user can write settings.php or change its permissions. Record that as a risk factor, not as proof the site is safe. - Note whether the site uses Drupal Steward. Steward coverage for known vectors does not remove the need to update. 2. Contain - If the fixed release is not installed, propose blocking the installer using the project's guidance. The report names a web-server deny rule, an .htaccess rule, or removing the file and keeping it removed with Composer scripts. If that guidance is not in front of you, stop and ask for it instead of writing a rule. - Ask before changing server config or deleting the file. 3. Remediate - Plan the version update for a supported branch and ask before applying it. - After the update, still plan to block the installer. The team recommends that even on fixed releases. 4. Verify - Confirm the running core version is the fixed release you intended, and that /core/install.php is not reachable from outside. 5. Report back - Versions found, whether the installer was reachable, what you updated or blocked, and any end-of-life sites that have no patch in this release. Do not invent CVEs, rewrite rules, or package versions. If a check needs access I have not given you, say what you need and stop.