Threat feed

CVE-2026-132165 — Drupal core installer (install.php) site takeover and code execution (Critical, fixed releases available): explainer and fix (SA-CORE-2026-017)

CVE-2026-132165: Drupal core install.php can lead to takeover or code execution. Update to 10.6.22, 11.3.22 or 11.4.13 (SA-CORE-2026-017).

Published 2026-11-20 Updated 2026-11-20 Last verified 2026-11-20 6 min read
On this page

For: IT, web and agency teams that run Drupal sites. This article is based on Drupal's advisory and the CISA KEV data; it does not cover attack steps.

続報待ち:この記事は公式発表に合わせて更新します

Who is affected

IT, web and agency teams that run Drupal sites.

Confirmed so farSee the table ↓
  • The flaw
  • Affected and fixed versions
  • Mitigation
1 more
  • Exploitation
Not yet confirmed
  • Publication of CVE-2026-132165 on CVE.org (we could not retrieve a CVE record as of November 20)
  • Whether it is exploited (no report found at publication)
  • Details and fixed versions of the companion advisory SA-CORE-2026-018 (CVE-2026-132166)
What to do nowSee the steps ↓
  1. Check your Drupal core version
  2. Update to a fixed release
  3. If you cannot update yet, protect install.php
3 more
  1. Update even if you use Drupal Steward
  2. Review the companion advisory
  3. Look for signs of compromise
Where to verify (source)All sources ↓
Drupal
Last checked
as of November 20, 2026
Follow-up plans and what we checked

Drupal's advisory SA-CORE-2026-017 was published on November 18. The materials we reviewed report no exploitation. It is not in CISA KEV as of November 20. The CVE.org record could not be retrieved as of November 20 (the number comes from Drupal's advisory).

What to do today

1

Check your Drupal core version

Use the status report in the admin UI or composer to confirm the core version. Affected: before 10.6.22, from 11.0.0 up to before 11.3.22, and from 11.4.0 up to before 11.4.13 (Drupal's advisory). If you run several sites, include development, staging and old maintenance sites (asset inventory checklist).

2

Update to a fixed release

Fixed: 11.4.13 for 11.4.x, 11.3.22 for 11.3.x, 10.6.22 for 10.6.x. 11.2.x and below and 10.5.x and below get no security coverage, and Drupal 8 and 9 are end of life; plan a move to a supported version. Back up and test on a staging copy before updating.

3

If you cannot update yet, protect install.php

Drupal's advisory says to follow its documentation on securing the installer until you can update. Press coverage also describes blocking access to core/install.php in the web server configuration or .htaccess. This is not a substitute for updating. The advisory also says some attack paths are blocked when the web server cannot write to or change permissions on settings.php, so review file permissions too.

4

Update even if you use Drupal Steward

The advisory says sites using Drupal Steward are protected from known attack vectors but should still update.

5

Review the companion advisory

The same day, SA-CORE-2026-018 (CVE-2026-132166, Moderately critical, 14/25) was published as a gadget chain. Read Drupal's advisory for its conditions and fixed versions.

6

Look for signs of compromise

Check for unexpected requests to install.php and for unfamiliar changes to settings.php or administrator accounts in the period before you update. No match does not prove you are clean. If anything looks wrong, isolate the site and rotate database and administrator credentials (how to check for intrusion).

What kind of flaw this is

Advisory summary — ADVISORY
CVE
CVE-2026-132165 (Drupal core: flaw involving the installer, install.php)
Advisory
SA-CORE-2026-017 (Critical, Remote code execution), November 18, 2026
Severity
Drupal risk 18/25 (AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon). CVSS not confirmed on CVE.org
Impact
Under specific conditions, an attempt to reinstall Drupal that can lead to site takeover or code execution (Drupal)
Affected
Before 10.6.22; 11.0.0 up to before 11.3.22; 11.4.0 up to before 11.4.13
Fix
11.4.13, 11.3.22, 10.6.22. 11.2.x and below and 10.5.x and below are unsupported
Exploitation
No report found at publication. Not in KEV as of November 20
18/25
Drupal risk rating (Critical)
11.4.13
Fix for 11.4.x
None
Confirmed exploitation (as of Nov 20)
  • In short: the install.php bundled with core can be used to try to reinstall a site that is already running. When conditions line up, that leads to takeover or code execution (Drupal). We do not include the specific conditions or requests.
  • In Drupal's rating, AC:Complex means specific conditions must be met, and A:None means no authentication is needed. TD:Uncommon is Drupal's target-distribution rating, indicating a configuration that is not common.
  • Some attack paths are blocked when the web server cannot change settings.php (Drupal's advisory).
  • It was found by an automated code-scanning tool; the advisory credits Drupal developers who reported and fixed it.

What is known and what is not

ItemContentStatus
The flawTakeover or code execution via a reinstall through install.phpConfirmed (Drupal)
Affected and fixed versions10.6.22, 11.3.22, 11.4.13; older branches unsupportedConfirmed (Drupal)
MitigationDrupal's documentation on securing install.php (not a substitute for updating)Confirmed (Drupal)
CVE.orgNo record could be retrievedNot confirmed as of November 20
ExploitationNo report at publication; not in KEVConfirmed (KEV data)
Exploit codeDrupal's rating includes E:ProofDrupal's rating; we did not review it and do not link to it

Sources

Attack steps and indicators of compromise (IOCs) are not included. Last verified: November 20, 2026.

Update history

2026-11-20: First report. Based on Drupal's advisory SA-CORE-2026-017 and the CISA KEV data; the pre-announcement is recorded separately as press coverage.

Latest breaking reports

All breaking reports →

FAQ

QWhat is CVE-2026-132165?
A

A flaw involving the installer (install.php) bundled with Drupal core. Per Drupal's advisory SA-CORE-2026-017, under specific conditions an attacker can use the installer to attempt to reinstall Drupal, which can lead to site takeover or remote code execution. Drupal's risk rating is Critical (18/25).

QWhich versions are affected and which are fixed?
A

Per Drupal's advisory, affected are versions before 10.6.22, from 11.0.0 up to before 11.3.22, and from 11.4.0 up to before 11.4.13. Fixed: 11.4.13 for 11.4.x, 11.3.22 for 11.3.x, 10.6.22 for 10.6.x. 11.2.x and below and 10.5.x and below get no security coverage, and Drupal 8 and 9 are already end of life.

QWhat if I cannot update right away?
A

Drupal's advisory says to follow its documentation on securing the installer (install.php) until you can update. Press coverage describes blocking access to core/install.php in the web server configuration or .htaccess. This is not a substitute for updating.

QIs it being exploited?
A

No exploitation was found in reporting at publication. Before the advisory, the Drupal security team reportedly warned that exploits could be developed within hours or days and urged administrators to prepare to update. It is not in CISA KEV as of 20 November.

QIf I use Drupal Steward, do I still need to update?
A

Yes. Drupal's advisory says sites using Drupal Steward are protected from known attack vectors but should still update.