CVE-2026-132165
Drupal core installer flaw can lead to site takeover or remote code execution; Drupal reports exploitation on live sites, fixed in 10.6.22, 11.3.22 and 11.4.13
Reachable if a site runs Drupal core below 10.6.22, 11.3.22 or 11.4.13, or an end-of-life branch, and /core/install.php can be reached over the network. Drupal's score says no login is needed. Drupal says the attack works only under specific conditions it hasn't described, and that some exploit paths are closed if the web server can't write to or change permissions on settings.php
Drupal says it has received a report that this flaw was exploited on live sites as early as November 19, 2026 at 19:00 UTC, and it now rates it Highly critical, 20/25, its top band. Under specific conditions, an attacker can use Drupal core's installer, install.php, to try to reinstall Drupal, which Drupal says "can lead to a site takeover or remote code execution." Drupal's score says no login is needed.
The fix is Drupal 11.4.13, 11.3.22 or 10.6.22, released November 18. Drupal 11.2.x and older, 10.5.x and older, and Drupal 8 and 9 are end of life and get no fix. If you can't upgrade right away, Drupal says to block the installer by following its guide to securing install.php, and it recommends doing that after upgrading too. Drupal also says some exploit paths are closed if the web server can't write to or change permissions on settings.php.
Drupal first rated it Critical, 18/25, on November 18 and raised it on November 20 with the exploitation report. Drupal has not said who reported the exploitation or how widely the flaw is being used. It is not on CISA's Known Exploited Vulnerabilities catalog as of the November 20, 2026 catalog, the CVE record has not been published, and we found no public exploit code. Anthropic's OSS Scanner found the flaw, per Drupal.
Is it reachable for you?
What it is. Drupal core ships an installer, install.php, that is meant to run once. Drupal says that under specific conditions an attacker can use it to try to reinstall Drupal, which can lead to a site takeover or remote code execution. Drupal has not described those conditions. Its score rates the attack as complex (AC:Complex), needing no login (A:None), with full impact on confidentiality and integrity, and affecting an uncommon share of sites (TD:Uncommon).
Who is most exposed. Internet-facing Drupal sites on an affected or end-of-life release where /core/install.php still answers, and especially sites where the web server can write to settings.php.
Checks, in three tiers. The first two decide exposure. The third decides priority. Run these only on sites your organization owns.
- Which Drupal core version runs? Check the Status report in the Drupal admin, or run composer show drupal/core. Anything below 10.6.22, 11.3.22 or 11.4.13 on its branch is affected, and 11.2.x, 10.5.x and older have no fix.
- Does the installer answer? Drupal's guide to securing the installer says to request /core/install.php, /install.php (following redirects) and /core/install.php/foo from outside. Each should return 403 or 404. A 200 means the installer is reachable.
- Can the web server write to settings.php? Drupal says some exploit paths are mitigated if the web server can't write to or change permissions on settings.php. Check the owner and permissions of each site's settings.php against the user the web server runs as. Sites where it can go first.
Compensating controls (test them, don't assume them)
Upgrading Drupal core is the fix. Until you can upgrade, Drupal says to follow its instructions for securing the installer, and it recommends keeping the installer blocked after upgrading too.
- Delivery. Block /core/install.php in the web server configuration, which Drupal's guide recommends because it keeps working through core updates. On Apache, deny the location in the virtual host configuration. On Nginx, use a prefix location that returns 404, and avoid an exact-match location, which the guide says can still pass /core/install.php/foo to PHP. Only if you test the configuration before reloading and don't need the browser installer, for example to add a site to a multisite.
- Delivery. On shared hosting, deny install.php in .htaccess, per Drupal. Only if Composer scaffolding won't overwrite .htaccess on the next update. Drupal's guide explains how to keep the rule through scaffolding.
- Delivery. Or delete core/install.php and remove it again after each Composer install or update, per Drupal. Only if every deploy runs those scripts, since composer install --no-scripts skips them.
- Exploitation. Make sure the web server can't write to or change permissions on settings.php. Drupal says this mitigates some exploit paths, so treat it as partial.
- Drupal Steward. Drupal says sites on Drupal Steward are already protected from known attack vectors, but should still upgrade in case new ones are found.
The patch is the only fix. Upgrade to Drupal 11.4.13, 11.3.22 or 10.6.22, or move off an end-of-life branch.
What to look for in logs
Drupal has published no indicators of compromise for this flaw as of November 21, 2026.
FAQ
Am I exposed to CVE-2026-132165?
You are if a site runs Drupal core below 10.6.22, 11.3.22 or 11.4.13, or an end-of-life branch, and /core/install.php can be reached over the network. Drupal says the attack works only under specific conditions, which it has not described, so treat any such site as exposed.
Is it being exploited?
Drupal says its Security Team received a report that the flaw was exploited on live sites as early as November 19, 2026 at 19:00 UTC, and its score marks an exploit as existing (E:Exploit). Drupal has not given details. It is not on CISA KEV as of the November 20, 2026 catalog, and we found no public exploit code.
Is there a fix for Drupal 11.2 or 10.5?
No. Drupal says 11.2.x and older and 10.5.x and older are end of life and get no security coverage, as are Drupal 8 and 9. Move to a supported release, and block the installer in the meantime.
Does blocking install.php fix it?
It blocks the installer, which is the path Drupal describes, and Drupal recommends it when you can't upgrade right away and after upgrading. Upgrading is the fix.
We use Drupal Steward. Are we covered?
Drupal says Drupal Steward sites are already protected from known attack vectors, but should still upgrade in case additional vectors are found.
- Vendor
- Drupal (Drupal Security Team)
- Product
- Drupal core
- Affected versions
- Drupal core before 10.6.22, 11.0.0 before 11.3.22 and 11.4.0 before 11.4.13, per Drupal. Drupal 11.2.x and older, 10.5.x and older, and Drupal 8 and 9 are end of life and get no fix
- Vulnerable component
- core/install.php, the Drupal installer
- CVSS
- Not scored. Drupal rates it Highly critical, 20/25 (AC:Complex/A:None/CI:All/II:All/E:Exploit/TD:Uncommon), raised from Critical, 18/25 on November 20. No CVE record or NVD entry yet
- CVSS vector
- Not published. Drupal's risk vector is AC:Complex/A:None/CI:All/II:All/E:Exploit/TD:Uncommon
- CWE
- Not published
- Exploitation
- Reported, not on KEV
- CISA KEV added
- Patch
- Drupal 11.4.13, 11.3.22 or 10.6.22 (November 18, 2026). End-of-life branches (11.2.x and older, 10.5.x and older, 8 and 9) get no fix and need to move to a supported release
Updates
Nov 21, 2026. First published. Drupal released fixes on November 18 and on November 20 raised the rating to Highly critical, 20/25, after a report that the flaw was exploited on live sites as early as November 19. Not on CISA KEV (catalog 2026.11.20).
Sources
- Drupal security advisory SA-CORE-2026-017 (published Nov 18, 2026; updated Nov 20 to Highly critical, 20/25, with the exploitation report; checked Nov 21)
- Drupal, Securing the installer (install.php) (updated Nov 18, 2026)
- Drupal releases 11.4.13, 11.3.22 and 10.6.22
- Drupal Steward
- CVE record CVE-2026-132165 (not yet published when checked Nov 21; no NVD entry)
- CISA Known Exploited Vulnerabilities catalog (not listed; checked catalog version 2026.11.20)
We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.