On this page (8 sections)

On 2026-11-18 the Drupal Security Team published SA-CORE-2026-017, a Critical advisory for Drupal core. The installer that ships with Drupal core, install.php, can under specific conditions be used by an attacker to attempt to reinstall the site. According to Drupal, that can lead to a site takeover or remote code execution.

If you run Drupal 10 or 11, or manage sites for clients who do, check your version today. Fixed releases exist, and the advisory also recommends securing the installer after installation, which is worth doing even on patched sites.

At a glance

What happened

Drupal core includes an installer script, install.php, for installing Drupal core. The advisory says that under specific conditions an attacker can use the installer to attempt to reinstall Drupal, which can lead to a site takeover or remote code execution.

The issue was discovered by Anthropic's OSS Scanner, tracked as ANT-2026-GMRPK0BU, and reported by members of the Drupal Security Team along with several contributors. The advisory lists a large group of security team members as fixers and coordinators.

Only the Drupal advisory covers this story so far, and the CVE has no NVD entry yet. Details such as a CVSS score may be added later, so re-check the advisory and NVD if you track severity formally.

Technical details

The advisory is brief on mechanics. It states that the installer can be used to attempt a reinstall under specific conditions, and that the outcome can be site takeover or remote code execution. It does not spell out what those conditions are.

It does give one concrete mitigation clue: some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. That makes file permissions a useful defense-in-depth control here, not just housekeeping.

The advisory also lists the risk vector AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon, with an overall rating of 18/25. We do not read more into those fields than the advisory states. It does not say that attacks have been seen in the wild.

General background, not the confirmed mechanism: a one-time installer is meant to run only when a site is first set up, so leaving it reachable on a live site is a recognized risk class. The advisory is why Drupal recommends securing the installer after installation in addition to upgrading.

Who is affected

Every Drupal core release below the fixed versions in these branches is affected:

Affected and fixed Drupal core versions (SA-CORE-2026-017)
BranchAffectedUpdate to
Drupal 11.4.x>=11.4.0 <11.4.1311.4.13
Drupal 11.3.x>=11.0.0 <11.3.2211.3.22
Drupal 10.6.x<10.6.2210.6.22
Drupal 11.2.x and below, 10.5.x and belowEnd-of-life, no security coverageMove to a supported branch
Drupal 8 and 9End-of-lifeMove to a supported branch

If you are on an end-of-life branch, Drupal does not provide security coverage for it. Plan an upgrade to a supported release rather than waiting for a backport.

Sites protected by Drupal Steward already have coverage against some known attack vectors. Drupal is explicit that this does not cover all possible exploits and that sites should still upgrade in the near future.

How to check your exposure

Start with the installed version. This Composer command lists the installed Drupal core package and its version; run it in your project root and compare the result with the fixed versions above.

Show the installed Drupal core version (run in the project root, Composer-managed sites)Shell
composer show drupal/core

If you use Drush, this prints the core version along with other site status details.

Show Drupal version and site status with Drush (run in the project root)Shell
drush status

Next, check whether the installer is reachable from the internet. This request prints only the HTTP status code for the install page; replace the hostname with your own. A 200 response on a live site deserves attention, while a 403 or 404 suggests the path is blocked or absent. A blocked response does not replace updating.

Check the HTTP status of install.php (run from any machine, replace example.com with your site)Shell
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/core/install.php

Finally, look at permissions on settings.php, since the advisory says some paths are mitigated when the web server cannot write to it or change its permissions. This read-only command shows the owner and mode; adjust the path to your docroot.

Show owner and permissions of settings.php (run on the server, adjust the path)Shell
ls -l /var/www/html/web/sites/default/settings.php

What to do now

  1. Identify every Drupal site you run, including staging, forgotten microsites and client installs.
  2. Back up the code, files and database before changing anything.
  3. Update to 11.4.13, 11.3.22 or 10.6.22, whichever matches your branch.
  4. If you are on 11.2.x or below, 10.5.x or below, or Drupal 8 or 9, schedule an upgrade to a supported branch now, since these receive no security coverage.
  5. Follow Drupal's instructions for securing the Drupal installer, which the Security Team recommends in addition to upgrading and as the interim step if you cannot upgrade immediately.
  6. Make sure the web server user cannot write to or change permissions on settings.php.
  7. Review web server logs for unexpected requests to install.php and for unexplained changes to settings.php or site configuration.
Caution. Run core updates on a staging copy first where you can, and take a backup before production. A rushed update on a heavily customized site can break custom modules or themes.

A typical Composer-based update looks like the commands below, which update core, run database updates and rebuild caches. This example is for the 11.4 branch; use 11.3.22 or 10.6.22 on those branches. Adjust to your own deployment process.

Update Drupal core to a fixed release (example for the 11.4 branch; run in the project root)Shell
composer require drupal/core-recommended:11.4.13 drupal/core-composer-scaffold:11.4.13 -W
drush updatedb -y
drush cache:rebuild
Tip. If you cannot patch today, securing the installer is the stopgap Drupal names in the advisory. Follow Drupal's official instructions for securing the Drupal installer for the exact method, then schedule the update.

Detection and monitoring afterwards

Search your access logs for hits on the installer, and alert on any change to settings.php or to your site's configuration that did not come from a deployment. This command lists the last 50 matching requests; adjust the log path and web server to your setup.

Search an access log for requests to install.php (run on the server, adjust the log path)Shell
grep -i "install.php" /var/log/nginx/access.log | tail -n 50

If you find successful requests you cannot explain, or signs that settings.php or admin accounts changed, treat the site as possibly compromised and follow a proper website hacked response. Our guide on how to check if a website is hacked covers the first checks.

For ongoing visibility, Webforta Monitor can watch uptime, certificates, DNS and header changes, and a read-only scan of a site you own can help you review what is exposed. Neither replaces patching.

What we still do not know

  • No CVSS score or NVD record exists yet for CVE-2026-132165.
  • The advisory does not say whether the flaw is being exploited in the wild.
  • The exact "specific conditions" for a successful attack are not spelled out beyond the mitigation around settings.php.

Treat the situation as time-sensitive anyway. The fix is released, the risk rating is Critical, and the update is routine for most teams.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. Drupal core - Critical - Remote code execution - SA-CORE-2026-017drupal.org ·
  • Drupal
  • RCE
  • CVE-2026-132165
  • PHP CMS
  • patching