The short version
- The flaw. Drupal core ships with an install.php file used to install the software. The Drupal Security Team says that under specific conditions an attacker can use that installer to attempt a reinstall, which can result in site takeover or remote code execution.
- Partial mitigation. Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. The team's guidance is to upgrade and, separately, to secure the Drupal installer once installation is finished.
- Steward cover is incomplete. Sites using Drupal Steward are already protected against some known attack vectors, but the team warns that this protection will not cover every possible exploit and says sites should upgrade in the near future in case more vectors emerge.
- Discovery and rating. The issue is advisory SA-CORE-2026-017, rated critical and published on 18 November 2026. The team credits Anthropic's OSS Scanner with finding it, tracked as ANT-2026-GMRPK0BU.
How the installer can be abused
Drupal core is distributed with an install.php script that sets the software up. The Drupal Security Team says that, under conditions it does not spell out in the advisory, an attacker can reach that script and use it to try to reinstall Drupal on the target site. A successful attempt can lead to a site being taken over or to remote code execution, meaning an attacker runs their own code on the server.
The team rates the issue critical and catalogues it as SA-CORE-2026-017. It credits Anthropic's OSS Scanner, which recorded the finding as ANT-2026-GMRPK0BU.
Protections and their limits
The advisory names two lines of defence besides patching. The first is file permissions: some exploit paths are mitigated when the web server cannot write to settings.php or change its permissions. The second is securing the Drupal installer after installation, which the security team recommends in addition to upgrading.
Drupal Steward, the vendor's protection service for participating sites, blocks some of the known attack vectors for this flaw. The team is explicit that this does not amount to full cover and that sites should still upgrade soon, in case further attack vectors are found.
What is not known yet
- Which Drupal core versions are affected, and which release carries the fix.
- What the specific conditions are that an attacker needs in order to abuse the installer.
- Whether anyone has already exploited the flaw in the wild.
- How many sites currently leave the installer reachable in production.
What to do
If you run Drupal
- Upgrade Drupal core as directed in advisory SA-CORE-2026-017.
- Secure or remove the Drupal installer after installation so install.php cannot be reached.
- Make sure the web server cannot write to settings.php or change its permissions.
- If you use Drupal Steward, keep it in place but upgrade anyway, because the team says its cover is incomplete.
For everyone else
- Remove or block installer and setup scripts from production web servers; a leftover installation file is a way in.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.