Security

Drupal Installer Vulnerability SA-CORE-2026-017: Update to 10.6.22, 11.3.22 or 11.4.13, Then Block install.php

A charcoal drawing with smudged shading of an architect's blueprint left unrolled on a plank table at a quiet building site at night, lit by one clamp work light, its corners held down by stones and a bare concrete foundation behind it, a visual for the Drupal installer vulnerability, where the original building plans were left out in the open

A Drupal installer vulnerability, SA-CORE-2026-017, can let an anonymous attacker use install.php to try to reinstall a live Drupal site, which can lead to site takeover or remote code execution. Drupal rated it Critical and fixed it on November 18, 2026, in Drupal 10.6.22, 11.3.22 and 11.4.13.

Drupal’s security team warned about this release two days early. It is the second critical Drupal core release in five weeks, after the one in our October 14 core security release post. This post explains what the advisory says, which versions are fixed, how to block the installer, and what Pantheon has done. Facts are as of November 20, 2026.

The short version: update core today. Then block web access to core/install.php, even after you patch, because Drupal recommends that for every installed site. Check that the web server cannot write to settings.php. If you still run Drupal 10, this is one of the last core security releases it will get before December 9.

What the Drupal installer vulnerability is

Drupal’s SA-CORE-2026-017 advisory is short. It says "Drupal core ships with an install.php file for installing Drupal core." Then: "Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal." And: "This can lead to a site takeover or remote code execution."

The advisory does not spell out the conditions. It gives one clue: "Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php." That file holds a site’s database connection and other core settings.

The advisory carries CVE-2026-132165. It credits Anthropic’s OSS Scanner with finding the bug. That scanner also found two of the fixes in this week’s WordPress 7.1.5 security release.

How Drupal scored it

Drupal scores advisories out of 25. This one scores 18, which is Critical. Drupal’s risk level definitions put Critical at 15 to 19. The parts of the score tell you more than the label:

  • No login needed (A:None). The attacker does not need an account.
  • Complex (AC:Complex). Drupal defines this as a "multi-step, unintuitive process with high number of dependencies."
  • Proof of concept (E:Proof). Drupal’s definition reads "documented methods for developing exploit exist in the wild." That is one step below a known working exploit.
  • Uncommon setups (TD:Uncommon). Only some configurations are exposed.
  • Full impact (CI:All, II:All). Every piece of data could be read or changed.

The PSA Drupal posted on November 16 was blunter. It said "More than one configuration is affected, so do not assume your site is safe." It also warned that "exploits might be developed within hours or days." Our guide to reading a CVSS score covers the similar CVSS system.

Which Drupal versions are fixed

You run Update to Note
Drupal 11.4.x 11.4.13 Current branch
Drupal 11.3.x 11.3.22 Supported until December
Drupal 10.6.x 10.6.22 Last Drupal 10 branch
Drupal 11.2.x or 10.5.x and below No fix End of life; move to a supported branch

The advisory says Drupal 11.2.x and below and Drupal 10.5.x and below "are end-of-life and do not receive security coverage." Drupal 8 and 9 are also long past end of life. If a site sits on an old minor, the fix is to update to a supported branch, not to wait for a backport. Our post on Drupal’s eight-month support rule explains why minors age out so fast. Our Drupal 12 RC1 post covers the 11.3 deadline.

The same releases fix a second issue. SA-CORE-2026-018 (CVE-2026-132166) is a Moderately critical "gadget chain." Drupal says "This issue is not directly exploitable." Drupal says it "presents no direct threat, but is a vector that can be used to achieve remote code execution" if combined with another flaw. The installer bug is the urgent one.

Block install.php, even after you patch

The advisory says "the Drupal Security Team recommends securing the Drupal installer after installation." An installed site has no use for install.php. Blocking it removes this Drupal installer vulnerability’s entry point, and any future one.

Drupal’s guide to securing the installer gives three options. It recommends the web server config.

Apache. Put this in the virtual host config, not in .htaccess. Drupal warns that a <Location> block in .htaccess causes a 500 error for the whole site.

<Location "/core/install.php">
  Require all denied
</Location>

Nginx. Add this inside the HTTPS server block, then run nginx -t before reloading.

location ^~ /core/install.php {
  return 404;
}

Drupal warns against an exact match (location = /core/install.php). On some setups it would miss a URL such as /core/install.php/foo.

Shared hosting. You can deny the file in .htaccess instead. On Composer-based sites, Composer overwrites .htaccess on every scaffold run. Drupal’s guide shows how to append your rule through composer.json so it survives.

Deleting the file is the third option. Composer restores it on every install or update, so you need a script to remove it each time. Drupal says the first two options are easier to maintain.

Two cautions from the same guide. Do not block update.php by accident, since you need it for database updates. And if you add multisite sites through the browser, you will need to allow the installer briefly, or use drush site:install.

To test the block, request /core/install.php and /core/install.php/foo on each site. Each should return 403 or 404. A 200 means the block is not working.

Check settings.php permissions

The advisory’s one clue points at settings.php. If the web server user can write to it, or change its permissions, more paths to the Drupal installer vulnerability are open.

Check this on every site you host yourself. If the web server account can write to settings.php or its folder, ask your host or sysadmin to make it read-only. Drupal’s installer guide suggests the Security Review module for checking file permissions and other common issues.

The fix also changes new installs. The Drupal 10.6.22 release notes say the installer used to try to fix settings.php permissions on its own. "Going forward, the installer will instead present an error message if the settings.php file is not writable." Drupal says this "does not impact existing sites."

What Pantheon and Acquia have done

Pantheon. Its November 18 release note on the Drupal installer vulnerability says "Pantheon’s runtime now blocks the installer once the site is installed, in all environments." It also deployed protections in advance as part of Drupal Steward. Pantheon still advises updating as soon as possible. Drupal 10 and 11 sites update core through Composer, with one-click core updates in the dashboard. For Drupal 7, Pantheon offers 7.109 through its long-term support with Tag1 Consulting. Pantheon says that update "removes install.php entirely."

Acquia. We found no public Acquia statement on this advisory as of November 20, 2026. Check Acquia’s support channels for platform-level blocking before you assume it is there. Our Pantheon vs Acquia comparison covers how each handles core updates.

Drupal Steward. The advisory says sites on Drupal Steward "are already protected from known attack vectors." That covers known paths only. Drupal still says to update.

The Drupal installer vulnerability and Drupal 10

Drupal’s 10.6.22 release notes say Drupal 10.6.x gets security coverage "until December 2026 when Drupal 11.5.0 is released." So a Drupal 10 site that patches today has a few weeks of coverage left.

Drupal 10 reaches end of life on December 9, 2026. After that, Drupal 10 core gets no more security releases. A future Drupal installer vulnerability or any other core bug would stay open on Drupal 10. See our Drupal 10 end-of-life guide and our plain-language guide to the Webform advisories for what to check now.

Contributed modules keep their own schedule. Our roundup of the November 4 and 11 contrib advisories lists 48 module fixes to apply alongside core.

How to apply the fix

These steps close the Drupal installer vulnerability on a typical Composer-based site.

  1. Update core with Composer. For example, composer update "drupal/core-*" --with-all-dependencies.
  2. Run database updates with drush updatedb, then clear caches.
  3. Confirm the version on each site’s Status report page.
  4. Block the installer at the web server, then test it.
  5. Check settings.php permissions on every site you host.
  6. Check logs for requests to install.php since November 18, and before it if you can.

What we do not know yet

Drupal has not described the "specific conditions" behind this Drupal installer vulnerability. As of November 20, 2026, neither Drupal’s advisory nor Pantheon’s note reports attacks on live sites. The E:Proof rating means documented methods exist, so treat attacks as likely.

Frequently Asked Questions

What is SA-CORE-2026-017?

A Critical Drupal core advisory from November 18, 2026. Under specific conditions, an attacker can use install.php to try to reinstall Drupal, which can lead to site takeover or remote code execution. It is CVE-2026-132165.

Which versions fix the Drupal installer vulnerability?

Drupal 11.4.13, 11.3.22 and 10.6.22. Drupal 11.2.x and below and 10.5.x and below get no fix because they are end of life.

Does an attacker need an account?

No. The advisory’s risk score marks it as needing no login. Drupal also rates the attack as complex and limited to uncommon setups.

Is it being exploited?

As of November 20, 2026, Drupal has not reported attacks. Its rating says a proof of concept exists, and its November 16 notice warned exploits might follow within hours or days.

Should we still block install.php after updating?

Yes. The Drupal Security Team recommends securing the installer after installation in addition to updating. An installed site does not need it.

Will blocking install.php break database updates?

No, if you block only install.php. Drupal’s guide warns against broad rules that also catch update.php, which you need for database updates.

We are on Pantheon. Are we covered?

Pantheon says its runtime now blocks the installer on installed sites in all environments, and that it deployed Drupal Steward protections in advance. It still says to update core as soon as possible.

What about Drupal 7?

Drupal.org’s advisory covers Drupal 10 and 11. Pantheon offers Drupal 7.109 through its long-term support, which it says removes install.php entirely. Ask your Drupal 7 support vendor.

What is SA-CORE-2026-018?

A second, Moderately critical advisory fixed in the same releases. Drupal calls it a gadget chain that is not directly exploitable on its own.

Digital Matters

Security Desk