Drupal has published SA-CORE-2026-017 — a security advisory, meaning an official notice that a vulnerability has been found and a fix is now available. This one is rated Critical, which is the highest severity level Drupal uses. It affects Drupal 10 and Drupal 11, and proof-of-concept exploits already exist publicly. The window for acting before the first automated scanning attempts closes fast.

The short version: update Drupal now, and block access to install.php if you haven't already.

This advisory is rated Critical (18/25 CVSS score) with known proof-of-concept exploits in the wild. Automated scanners will begin probing for unpatched sites within hours of publication. If your site is managed by an agency or developer, forward this to them immediately.

What the vulnerability actually is

Every Drupal installation includes a file called install.php — it's the script that runs the first-time setup process when you install Drupal on a fresh server. Once your site is set up, you don't need it any more. But it doesn't go away on its own.

The vulnerability in SA-CORE-2026-017 allows an attacker to use that installer file to attempt to reinstall Drupal on your running site, under specific conditions. If successful, this could mean a complete site takeover or remote code execution — the ability to run arbitrary commands on your server. That's about as serious as it gets.

Drupal 8 and Drupal 9 are not covered by this advisory — but only because both reached end of life (meaning they no longer receive any security support), not because they're safe. If your site runs either of those versions, it has its own set of unpatched vulnerabilities and migration is overdue.

Which versions are affected

Drupal version Affected? Fix
Drupal 11.4 Vulnerable Update to 11.4.13 or later
Drupal 11.0–11.3 Vulnerable Update to 11.3.22 or later
Drupal 10 Vulnerable Update to 10.6.22 or later
Drupal 9 End of life No patch. Migration required.
Drupal 8 End of life No patch. Migration required.
Drupal 7 Not in scope D7 has separate EOL concerns — see below

Step 1: Update Drupal core

The proper fix is to update. This advisory requires no database or configuration changes, so a standard Composer update is all that's needed. If your site is managed with Composer — the standard way of handling Drupal dependencies — the command is:

composer update "drupal/core*" -W

The -W flag updates all drupal/core* packages along with their dependencies in one go. Once that's done, clear the cache:

drush cr

If you're not sure how your site is managed, your developer or hosting provider will know. Don't attempt a Drupal core update manually without understanding how the site is deployed — a botched update is worse than a brief delay.

Recommended: block access to install.php

Updating fixes this specific vulnerability. But blocking install.php at the web server level is a sensible permanent measure — once a site is running, the installer script serves no purpose and there's no reason to leave it exposed. Drupal recommends it, and it's worth doing while you're already making changes.

There are three ways to do it depending on your setup.

Apache — virtual host configuration (recommended)

Add this to your Apache virtual host configuration file (not .htaccess), then test and reload:

<Location "/core/install.php">
  Require all denied
</Location>
apachectl configtest && apachectl graceful

Nginx

Add this inside your server block, then test and reload:

location ^~ /core/install.php {
  return 404;
}
nginx -t && nginx -s reload

The ^~ modifier ensures this rule takes priority and also blocks URLs with anything appended after install.php.

Apache on shared hosting (.htaccess)

If you're on shared hosting without direct access to the virtual host config, add this to the .htaccess file in your web root:

<Files "install.php">
  Require all denied
</Files>

Using Composer to manage your Drupal site? Composer can regenerate .htaccess during updates, which would remove any manual additions. The safer approach is to add the block via your server config, or use Composer scripts to delete install.php entirely (see below).

Delete install.php via Composer scripts

The most permanent solution is to remove the file entirely after every install or update. Add these scripts to your composer.json:

"scripts": {
    "post-install-cmd": ["rm -f web/core/install.php"],
    "post-update-cmd": ["rm -f web/core/install.php"]
}

Adjust the path (web/core/) to match your project's document root if it's different.

Verify the block is working

Once you've made the change, test all three URL variants — attackers use variations to work around naive blocking rules:

curl -I https://yourdomain.co.uk/core/install.php
curl -IL https://yourdomain.co.uk/install.php
curl -I https://yourdomain.co.uk/core/install.php/foo

All three should return a 403 Forbidden or 404 Not Found response. If any return a 200 OK, the block isn't working.

A note on Drupal 7

Drupal 7 is not covered by this specific advisory, but that's cold comfort: Drupal 7 reached end of life in January 2025 and no longer receives any security fixes at all. It sits outside the scope of advisories like this one not because it's safe, but because nobody is maintaining it. If your site is running Drupal 7, the right question isn't about this week's advisory — it's about planning a migration to a supported version.

If you're not sure which version of Drupal your site is running, we can check that for you as part of a free security review.