CRITICAL DRUPAL CORE SECURITY ADVISORY
Decision: Drupal sites in the affected ranges should move to a fixed supported release. Under specific conditions, the installer can be used to attempt a reinstall, which can lead to site takeover or remote code execution.[1]
Identifier: SA-CORE-2026-017, published November 18, 2026, covers CVE-2026-132165.[1][3]
Reporting cutoff: November 19, 2026, 9:55 a.m. EST / November 19, 2026, 14:55 UTC.

Who is exposed
The issue is conditional: Drupal says an attacker can use the installer to attempt a reinstall only under specific conditions. Some paths are mitigated when the web server cannot write to or change permissions on settings.php.[1]
| Branch | Affected range | Minimum fixed release |
|---|---|---|
| Drupal 10 | Below 10.6.22 | 10.6.22[1] |
| Drupal 11.0–11.3 | 11.0.0 through 11.3.21 | 11.3.22[4] |
| Drupal 11.4 | 11.4.0 through 11.4.12 | 11.4.13[4] |
End-of-life branches need a supported migration
Drupal 11.2 and below, Drupal 10.5 and below, and Drupal 8 and 9 are end-of-life and do not receive security coverage under these fixed releases.[1]
What to do now
- Inventory the exact core version. Compare it with the three affected ranges; do not infer exposure from Drupal branding alone.[3]
- Update supported branches. Move to 10.6.22, 11.3.22 or 11.4.13, as applicable.[1]
- If an immediate update is not possible, secure the installer. Drupal says the installer is at
/core/install.phpand should be blocked after installation; its verification guidance says requests should end with a 403 or 404 response rather than 200.[2] - Review the
settings.phppermission boundary. Check, without changing it during inspection, whether the web server can write to the file or change its permissions; Drupal says inability to do so mitigates some exploit paths, not all paths.[1]
Important limits
Drupal Steward protects against some known attack vectors, but Drupal says it does not cover all possible exploits; Steward customers should still upgrade.[1]
The CVE Program API returned no CVE record for CVE-2026-132165 at the cutoff. This is an availability finding, not a reason to reject the identifier carried by Drupal and OSV.[5][3]
Sources
- Drupal SA-CORE-2026-017 (accessed November 19, 2026).
- Drupal: Securing the installer (install.php) (accessed November 19, 2026).
- OSV: DRUPAL-CORE-2026-017 (accessed November 19, 2026).
- Drupal Security Team advisory database (accessed November 19, 2026).
- CVE Program API availability check (accessed November 19, 2026).
