The Drupal Security Team released Drupal 10.6.22, 11.3.22, and 11.4.13 on November 18, 2026. The releases fix two core issues, SA-CORE-2026-017 and SA-CORE-2026-018. Drupal is not a Windows product. It is, however, a CMS that large organisations, universities and government bodies run, so it often sits in the same estate that Windows and enterprise admins look after. The advisories are the primary evidence here. BleepingComputer's report and several secondary trackers corroborate them.
What the critical flaw is
The critical issue is CVE-2026-132165 (SA-CORE-2026-017). Drupal rates it Critical, 18/25, as a remote code execution vulnerability. Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. That can lead to site takeover or remote code execution.
- Discoverer: The advisory credits Anthropic's OSS Scanner, under the reference ANT-2026-GMRPK0BU. BleepingComputer adds that anonymous users can exploit the flaw.
- Partial mitigation: Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. That is a helpful hardening layer, not a fix.
- What is not public: The advisory gives no exploit recipe and does not list every condition an attacker needs. Don't assume every Drupal site is exploitable. Don't assume yours is safe either.
Who is affected and what to install
The affected ranges are anything before 10.6.22, 11.0.0 up to before 11.3.22, and 11.4.0 up to before 11.4.13. The same ranges apply to the second advisory.
| Your branch | Update to |
|---|---|
| Drupal 11.4.x | 11.4.13 |
| Drupal 11.3.x | 11.3.22 |
| Drupal 10.6.x | 10.6.22 |
Drupal 11.2.x and below are end-of-life and do not receive security coverage. The same applies to 10.5.x and below, and to Drupal 8 and 9. If you are on one of those branches, the listed patches are not available to you. Your real task is to plan a move to a supported branch.
Composer-managed sites can use a command like this, shown here for 11.4.x. Third-party coverage from Azeem Hassni includes this exact form:
composer require 'drupal/core:11.4.13' --update-with-dependencies
Adjust the version for your branch, and test in staging first.
The second advisory: CVE-2026-132166
SA-CORE-2026-018 is rated Moderately critical, 14/25. It describes a "gadget chain" in core. Drupal's wording is that this issue is not directly exploitable. It only becomes dangerous if a separate vulnerability lets an attacker pass unsafe input to unserialize(). It shouldn't be described as a standalone RCE. It is still worth patching, because it makes any future deserialization bug in a Drupal site more dangerous.
Why the warning is urgent
Drupal gave advance notice on November 16 that the release would land on November 18. The team warned that exploits might be developed within hours or days, and that at least one of the flaws could be exploited by anonymous users.
That is a prediction, not a report of attacks. Securityonline's tracker lists both CVEs as not exploited at the time of its writing. Drupal's recent record explains the caution:
- In May, Drupal confirmed active exploitation of an SQL injection flaw, CVE-2026-9082.
- BleepingComputer also notes a more recent Commerce Core access bypass, CVE-2026-118539, being abused in attacks.
- CISA has flagged five Drupal vulnerabilities as exploited since November 2021, two of them used in ransomware attacks.
Patch diffs and advisories give attackers a head start. This one is also an installer reinstall bug, so it is simple to describe and to scan for.
If you can't upgrade today
Drupal's guidance is to block access to the installer. The documentation, updated November 18, puts the installer at /core/install.php. It is needed only to install a site, including a new site in a multisite setup. Blocking it does not affect updates, because update.php is a separate script.
Apache (preferred, in server configuration)
Put this in the virtual-host or server configuration, not in .htaccess:
<Location "/core/install.php">
Require all denied
</Location>
- Add it to every virtual host that serves the site, including the HTTPS one. You can also place it once outside any virtual-host block.
- Run
apachectl configtest, then reload Apache. - If Drupal lives in a subdirectory, change the path to match.
Drupal warns that <Location> is not allowed in .htaccess. Putting it there makes the whole site return a 500 error. Visitors who hit the blocked path get a 403.
Nginx
Add this inside the HTTPS-serving server block:
location ^~ /core/install.php {
return 404;
}
Run nginx -t before you reload. The ^~ prefix also catches paths with extra text after the filename, such as /core/install.php/foo. Do not use an exact-match rule. Some Nginx setups send any .php/ path to PHP, so an exact match would leave that variant reachable.
Apache .htaccess fallback
If you can't edit server configuration, for example on shared hosting, use this in the web-root .htaccess:
<Files "install.php">
Require all denied
</Files>
- Apache must allow
Requirerules there, which meansAllowOverrideincludesAuthConfig. Drupal says its normal setup generally covers this. - Composer-based sites need extra care. The scaffold step can overwrite manual
.htaccessedits, even on a plaincomposer install. - Drupal documents keeping the rule in a separate file and configuring the scaffold plugin to append it.
Removing the file
Deleting core/install.php is an option, but Composer restores it whenever core is installed or updated. Drupal documents Composer scripts that remove it again. They don't run if you use composer install --no-scripts. Drupal says server configuration or .htaccess blocking is easier to maintain for most sites.
Check that it worked
Drupal's documentation suggests running these three requests against your own site:
curl -I [url]https://example.com/core/install.php[/url]
curl -IL [url]https://example.com/install.php[/url]
curl -I [url]https://example.com/core/install.php/foo[/url]
All three should end in a 403 or 404. A 200 means the block isn't working. Then confirm that the site still works and that database updates still run through drush updatedb or /update.php.
Some managed hosts already block the installer. Pantheon, for example, says its runtime blocks it once a site is installed. Check with your host before adding your own rule.
What Drupal Steward does and doesn't do
Drupal says this issue is being protected by Drupal Steward, its paid WAF service. Sites on Steward are already covered against known attack vectors. Drupal still tells them to upgrade soon in case other vectors are found. Treat the WAF as a temporary shield.
Practical checklist
- Inventory every Drupal site and note its branch and exact version, including forgotten multisite members and staging copies.
- Update to 10.6.22, 11.3.22 or 11.4.13 as appropriate.
- Block
/core/install.phpat the server level, and verify with the three requests above. - Check that
settings.phpis not writable by the web server user. - Plan migrations off end-of-life branches.
- Review logs for unexpected requests to the installer path since the disclosure. This is general good practice, not something the advisories specifically require.
This is a good reminder that leftover setup tools are attack surface. The installer is needed once, and then it is just a liability that has to be blocked.
References
- Drupal patches critical RCE flaw, warns exploits may surface quickly BleepingComputer · 2026-11-19T08:08:08-05:00
- Drupal core - Critical - Remote code execution - SA-CORE-2026-017 drupal.org
- Drupal core security releases fix a critical remote code execution issue docs.pantheon.io