Drupal's Security Team published SA-CORE-2026-017 on 18 November 2026: a Critical remote code execution flaw (CVE-2026-132165) in which the core installer, install.php, can be abused under specific conditions to try to reinstall Drupal, which can lead to site takeover. The fix is Drupal 10.6.22, 11.3.22 or 11.4.13. If you cannot update today, block /core/install.php in your web server configuration and update as soon as you can.
BleepingComputer reported on 19 November 2026 that the Drupal Security Team warned exploits might surface within hours or days. This guide separates what Drupal states from what others report, shows how to tell whether you are affected, and lists the update and mitigation steps from Drupal's own documentation.
What happened
All of the following comes from Drupal's advisory unless attributed otherwise.
| Date | What was published | Source |
|---|---|---|
| Monday before release (exact date not given) | The Drupal Security Team issued an advance warning, according to BleepingComputer | BleepingComputer, 19 Nov 2026 |
| 18 Nov 2026 | SA-CORE-2026-017 (CVE-2026-132165), Critical, risk score 18/25 | drupal.org advisory |
| 18 Nov 2026 | SA-CORE-2026-018 (CVE-2026-132166), Moderately critical, 14/25, a gadget chain | drupal.org advisory |
| 19 Nov 2026 | BleepingComputer reports on both advisories | BleepingComputer |
The advisory describes the vulnerability as: the Drupal core installer (install.php) can be abused under specific conditions to attempt a reinstall of Drupal, and successful abuse can lead to site takeover or remote code execution. Its risk vector lists no authentication required, full confidentiality and integrity impact, a proof of concept available, and exploitation limited to uncommon configurations. BleepingComputer's summary says anonymous users can exploit the flaw to reinstall Drupal; the advisory's wording is more cautious ("under specific conditions"), so treat the specific conditions as the deciding factor and do not assume your site is safe.
The advisory credits the discovery to Anthropic's OSS Scanner, reported by members of the Drupal Security Team and other contributors, with the fix coordinated by the Drupal Security Team.
Claims and unknowns
| Statement | Who said it | Status |
|---|---|---|
| A proof of concept exists | Drupal advisory | Stated by the vendor |
| Exploits might be developed within hours or days | Drupal Security Team, as reported by BleepingComputer | A warning, not a report of attacks |
| Active exploitation of CVE-2026-132165 | Not stated in the advisory or the BleepingComputer report | Not reported as of 20 Nov 2026 |
| Number of affected sites | Not published | Unknown |
BleepingComputer also listed earlier Drupal issues for context: it reported CVE-2026-9082, an SQL injection in the database abstraction API, as confirmed actively exploited in May, and CVE-2026-118539 in the Commerce Core module as being abused in attacks. Those are separate from this advisory.
Am I affected?
You are in scope if your site runs Drupal core in one of these ranges (from the advisory):
| Branch | Affected | Fixed in |
|---|---|---|
| Drupal 10 | All versions before 10.6.22 | 10.6.22 |
| Drupal 11.3.x | Before 11.3.22 | 11.3.22 |
| Drupal 11.4.x | Before 11.4.13 | 11.4.13 |
| Drupal 11.2.x and earlier, 10.5.x and earlier, Drupal 8, Drupal 9 | End of life, no security coverage | No fix; move to a supported branch |
The second advisory, SA-CORE-2026-018 (CVE-2026-132166), lists Drupal core before 10.6.22, 11.0.0 up to before 11.3.22, and 11.4.0 up to before 11.4.13. The advisory says it is "not directly exploitable": it describes a chain of methods that could become a remote code execution vector only if a site has a separate insecure deserialization flaw that passes untrusted data to unserialize(). Exploit maturity is rated theoretical, and the advisory names no workaround beyond updating.
No indicators of compromise have been published in the advisory or the BleepingComputer report, so this article lists none. Check which version you run:
composer show drupal/core | grep versionsDrupal's update guide says the Status report page in the admin UI shows the version Drupal is actually running; if the two disagree, a failed update may be the cause.
Managed hosts may already block the installer, so also check with your host. Drupal's installer guidance notes that some managed hosts block it already.
What to do now
- Update Drupal core to 10.6.22, 11.3.22 or 11.4.13, depending on your branch (steps below).
- If you cannot update immediately, block access to
/core/install.phpat the web server (steps below) and make sure the web server cannot write to or change permissions onsettings.php. - If you run an end-of-life branch, plan a move to a supported branch; the advisory says there is no security coverage for it.
- Test that the installer is blocked and that the site and
update.phpstill work. - Review your access and web server logs for requests to
install.php. Drupal has not published log patterns, so treat any unexpected request as something to investigate.
Update with Composer
Drupal's guide gives these commands. If the project uses drupal/core-recommended:
composer update "drupal/core-*" --with-all-dependenciesIf it uses only drupal/core:
composer update drupal/core --with-dependenciesCheck which you use with composer show drupal/core-recommended. Add --dry-run to preview changes. Then run database updates and rebuild caches:
drush updatedb
drush cache:rebuildWithout Drush, open [YOUR DOMAIN]/update.php in a browser for the database updates. If the Composer version and the Status report page disagree, Drupal's guide says to delete the web/core/ directory, run composer install, then rebuild caches.
Block install.php
Drupal's page "Securing the installer (install.php)" describes three options: web server configuration (recommended, because it keeps working when you update core), .htaccess on Apache where you cannot edit server configuration, or removing the file.
For Apache, add this to the virtual host configuration, not .htaccess:
<Location "/core/install.php">
Require all denied
</Location>For nginx, inside the HTTPS server block:
location ^~ /core/install.php {
return 404;
}The page warns against an exact match (location = /core/install.php), because some configurations pass URLs containing .php/ to PHP, which would leave the installer reachable. For .htaccess in the web root:
<Files "install.php">
Require all denied
</Files>The page warns that Apache does not allow <Location> in .htaccess and that doing so causes a 500 error for the whole site. It also says to add the rule to every virtual host serving the site, including the HTTPS one, and to run apachectl configtest or nginx -t before reloading. Blocking install.php does not affect update.php, but a broad rule could block it by accident.
To verify, the page suggests using curl against install.php, the /install.php path and a /core/install.php/foo path, expecting 403 or 404; a 200 means the block is not working.
Keep settings.php protected
The advisory says some exploit paths are blocked if the web server cannot write to or change permissions on settings.php. Drupal's file permissions guide says settings.php contains the database password and username in plain text and that it "must be set so that only appropriate users can read it," which usually means removing read permissions for "other."
How to prevent it
- Subscribe to Drupal security announcements and apply core updates on a routine schedule, not only for critical ones.
- Keep the installer blocked at the web server permanently; the recommended method keeps working across core updates.
- Run only supported branches. Drupal 8, Drupal 9, 10.5.x and earlier, and 11.2.x and earlier receive no security coverage.
- Keep
settings.phpand file ownership locked down using the commands in Drupal's "Securing file permissions and ownership" guide. - Consider Drupal Steward, a paid service, as an extra layer. The advisory says it protects against known attack vectors for this issue, but you should still upgrade.
For general patching habits across a PHP stack, see our related guide PHP security release 19 November 2026.
What we checked
- Opened the BleepingComputer article on 2026-11-20 and the Drupal advisory SA-CORE-2026-017 (primary source) on 2026-11-20. Fixed versions 10.6.22, 11.3.22 and 11.4.13 match on both.
- Opened SA-CORE-2026-018 on 2026-11-20; its fixed versions match those in SA-CORE-2026-017.
- Mitigations (restricting write access to
settings.php, securinginstall.php, Drupal Steward) are from the advisory. Server snippets and verification steps are from Drupal's installer guide, opened 2026-11-20. - Composer, Drush and version-check commands are from Drupal's "Updating Drupal core via Composer" page, opened 2026-11-20.
- Not verified: BleepingComputer's statement that anonymous users can exploit the flaw, and its "hours or days" quote, are not repeated in the advisory text we read. The advance warning date was not confirmed. The
install.phpguidance page did not list affected-version specifics. - Not tested on a live Drupal site; commands are copied from Drupal's documentation and were not run.
Last tested: 2026-11-20
Sources
- Drupal Security Team, SA-CORE-2026-017: https://www.drupal.org/sa-core-2026-017
- Drupal Security Team, SA-CORE-2026-018: https://www.drupal.org/sa-core-2026-018
- Drupal documentation, Securing the installer (install.php): https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-the-installer-installphp
- Drupal documentation, Securing file permissions and ownership: https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-file-permissions-and-ownership
- Drupal documentation, Updating Drupal core via Composer: https://www.drupal.org/docs/updating-drupal/updating-drupal-core-via-composer
- BleepingComputer, 19 Nov 2026: https://www.bleepingcomputer.com/news/security/drupal-patches-critical-rce-flaw-warns-exploits-may-surface-quickly/
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.