top of page

Drupal's Installer Can Be Used to Reinstall Your Site (SA-CORE-2026-017, CVE-2026-132165). Update to 10.6.22, 11.3.22 or 11.4.13, Then Block core/install.php for Good

Writer: Patrick Duggan
Patrick Duggan
31 minutes ago
5 min read

If you run Drupal 10 or 11, do two things today. First, update core: 11.4.x to 11.4.13, 11.3.x to 11.3.22, 10.6.x to 10.6.22. Second, block the installer at core/install.php and keep it blocked, even after you update. The Drupal Security Team recommends both, and the second one costs you a few lines of web server config.


The advisory is SA-CORE-2026-017, CVE-2026-132165, published Wednesday, November 18, 2026, rated Critical, 18 out of 25. Drupal warned it was coming two days earlier (PSA-2026-11-16) and told site owners that exploits may appear within hours or days of release.



What Drupal says


Drupal core ships with an installer, install.php. The advisory's words: "Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal." Success can mean site takeover or remote code execution.


The advisory does not spell out what those "specific conditions" are. Its risk string gives the shape: AC:Complex (attack complexity is complex), A:None (no login needed), CI:All and II:All (full confidentiality and integrity impact), E:Proof (a proof of concept exists), TD:Uncommon (the vulnerable configuration is uncommon on default installs). It names one partial brake: "Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php."


Affected: Drupal 10 before 10.6.22, Drupal 11.0.0 before 11.3.22, and Drupal 11.4.0 before 11.4.13.


Fixed: 11.4.13, 11.3.22, 10.6.22.


No fix: Drupal 11.2.x and earlier, Drupal 10.5.x and earlier, and Drupal 8 and 9 are end of life and get no security release. If you are on one of those, the installer block below is not optional, and neither is planning the upgrade. The Hacker News reports that 154,485 of 528,430 sites reporting usage data to drupal.org (about 29%) ran end-of-life branches in the week of November 8. That population is sites that report usage, not every Drupal site.


Drupal 7 is not listed as affected.


The same release fixes a second issue, SA-CORE-2026-018 (CVE-2026-132166), rated Moderately critical, 14 out of 25: a "gadget chain" in core that the advisory says "is not directly exploitable" and only matters alongside another flaw. Same fixed versions, so one update covers both.


The advisory credits the discovery to Anthropic's OSS Scanner.



What is not known


Exploitation in the wild: the advisory does not report any, and CVE-2026-132165 is not in CISA's Known Exploited Vulnerabilities catalog (we checked the KEV JSON, catalog version 2026.11.18, released 19:17 UTC on November 18). "Proof" in Drupal's scale means a proof of concept exists, not that attacks are happening. We have harvested no public proof-of-concept repository for this CVE as of this morning.


Indicators: none published in the sources we read. We have added nothing to the feed for this one.



What to do


  1. Update core to 11.4.13, 11.3.22 or 10.6.22. On Composer sites that is an update of drupal/core-recommended (or drupal/core) followed by your normal database update step (drush updatedb or /update.php).

  2. Block the installer. Drupal's guide, "Securing the installer (install.php)" at drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-the-installer-installphp, gives three ways. The one it recommends is a web server rule, because it survives core updates. On Apache, a Location block for /core/install.php with "Require all denied" in the virtual host config (not .htaccess), applied to every virtual host including HTTPS. On nginx, a prefix location for /core/install.php that returns 404. The guide warns against an exact-match nginx location, because a request for /core/install.php/foo can still reach the installer on some configs. If Drupal lives in a subdirectory, the path changes to match, for example /drupal/core/install.php.

  3. If you cannot touch the server config, the guide's other options are an .htaccess rule for install.php (Apache only; Composer scaffolding overwrites .htaccess, so add it through file-mapping in composer.json) or deleting core/install.php with Composer post-install and post-update scripts (it comes back on every core update, and composer install with --no-scripts skips the removal).

  4. Make settings.php read-only to the web server user. The advisory says that closes some exploit paths. It is also how Drupal has always wanted that file.

  5. Drupal Steward customers are reported to be protected from the known attack vectors. Update anyway; the advisory says so too.


Am I affected?


Check three things.


Your version. Log in as an admin and open Reports, then Status report (/admin/reports/status); the Drupal version is the first line. From the shell, drush status prints it. On a Composer site, composer show drupal/core prints the installed version, and composer.lock has it under drupal/core. In the code itself, core/lib/Drupal.php holds a line const VERSION with the exact string. Anything below 10.6.22, 11.3.22 or 11.4.13 (on its branch) is affected.


Whether the installer answers. Drupal's guide gives three requests to run against your own site with curl -I (headers only): https://your-site/core/install.php, https://your-site/install.php (with -L to follow redirects), and https://your-site/core/install.php/foo. All three should end in 403 or 404. "If you see 200, the block is not working." Run them against every hostname that serves the site, including any origin hostname that bypasses your CDN.


Whether settings.php is writable by the web server user. Look at the owner and mode of sites/default/settings.php (and any other site directories under sites/). If the user your PHP runs as can write it, fix that.



What our edge saw


We ran our edge check for "install.php" across the last 30 days (since October 20): 550,543 edge block records, 94,723 edge canary records and 695 origin honeypot captures scanned.


Requests for Drupal's actual installer path, /core/install.php: zero, in all three.


What did match was generic. Four blocks for a bare /install.php from three IP addresses (two on Microsoft's AS8075, one on AS31898), on November 9, 12 and 18, and twelve canary hits on WordPress installer paths such as /wp-admin/install.php. A bare /install.php is a path many applications use, and the WordPress paths are WordPress. None of it is evidence of anyone trying CVE-2026-132165, and we are not counting it as such. One of those Microsoft-hosted addresses hit both a bare /install.php and /wp-admin/install.php at 17:00 UTC on November 18, the same hour the Drupal release window opened; it had probed /wp-admin/install.php twice earlier in the week too, so this reads as a routine installer sweep, not a reaction to the advisory. None of our own pages matched the pattern.


Our edge only sees requests to our own sites, and we do not run Drupal. Zero on /core/install.php means no one asked us for it, not that nobody is scanning for it.



How we know


We read SA-CORE-2026-017, SA-CORE-2026-018, PSA-2026-11-16 and Drupal's installer hardening guide on drupal.org, the CISA KEV JSON, and The Hacker News report. Version numbers, risk scores, the settings.php mitigation and the Steward note come from the advisory. The usage figure is from The Hacker News, which also reports that Drupal 11.3.x and Drupal 10 lose security coverage in December; we did not confirm that date on drupal.org. The edge figures come from our own block, canary and honeypot records.



Sources


Drupal Security Team, SA-CORE-2026-017, Drupal core, Remote code execution: https://www.drupal.org/sa-core-2026-017


Drupal Security Team, SA-CORE-2026-018, Drupal core, Gadget chain: https://www.drupal.org/sa-core-2026-018


Drupal Security Team, PSA-2026-11-16: https://www.drupal.org/psa-2026-11-16


Drupal, Securing the installer (install.php): https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-the-installer-installphp


CISA Known Exploited Vulnerabilities catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog


The Hacker News, "Drupal Patches Critical Installer Flaw That Could Give Unauthenticated Attackers Control of Sites"





Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page