What to check first
The new advisories dated November 18 (UTC) cover two core issues and no contributed-project issues. The official listing and RSS agree on SA-CORE-2026-017 and 018. One is Critical and one is Moderately critical, with two CVEs. The November 16 PSA is excluded from these counts.
Check your installed core branch and prioritize 11.4.13 for 11.4.x, 11.3.22 for 11.3.x, or 10.6.22 for 10.6.x. Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8/9 have reached end of security coverage. Read each official advisory for applicability and upgrade guidance.
- Existing-site administrators can review installer protection and advisory 017 .
- Sites using contributed or custom code can review advisory 018 and unsafe deserialization .
- New installations should also review the changed
settings.phppermission handling and post-installation protection in the release review .
Official advisory listing ↗ · All-advisory RSS ↗
Drupal core
Machine name drupal
| Official advisory, CVE and date | Severity | Affected versions | Official fixed releases |
|---|---|---|---|
| SA-CORE-2026-017 ↗
CVE-2026-132165 2026-11-18 |
Critical 18/25 | <10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13 |
11.4.13 ↗ · 11.3.22 ↗ · 10.6.22 ↗ |
| SA-CORE-2026-018 ↗
CVE-2026-132166 2026-11-18 |
Moderately critical 14/25 | <10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13 |
11.4.13 ↗ · 11.3.22 ↗ · 10.6.22 ↗ |
SA-CORE-2026-017 Remote code execution through the installer
Under specific conditions, an anonymous attacker can attempt reinstallation through install.php, leading to site takeover or remote code execution. Preventing the web server from modifying settings.php or changing its permissions mitigates some exploit paths. The official assessment includes AC:Complex and A:None.
Upgrade core and secure the installer after installation. If an immediate upgrade is unavailable, follow the official installer-protection instructions. Drupal Steward covers some known attack vectors; an upgrade remains necessary. Official advisory ↗ · Installer protection ↗
SA-CORE-2026-018 Gadget chain combined with unsafe deserialization
A chain of core methods could enable remote code execution when another vulnerability lets an attacker pass untrusted input to unserialize(). The advisory rates this AC:Complex and A:Admin. Exploitation requires that separate unsafe-deserialization vulnerability; this issue is not directly exploitable on its own. Check contributed and custom code as well. Official advisory ↗
Administrator checklist
- Identify your core version and support status. Compare with the official fixed releases and prepare a tested backup and development copy.
- Update the supported branch, then perform database updates and cache rebuilding according to your deployment process. See the core update guide .
- After installation, restrict public access to
core/install.phpusing the official instructions. Choose protection that survives Composer operations. - Check that
/core/install.php, redirects from/install.php, and/core/install.php/fooend in 403 or 404, adapting paths to your installation. Verify normal pages, login and database updates too. - For new installations, account for the fixed installer reporting an error when
settings.phpis unwritable. Review permissions and protection after installation finishes.
These checks summarize official advisories and installer guidance. No running-Drupal update or access-blocking test was performed for this review. Official installer guidance ↗
Guide review
3.7 Running the installer now covers permission handling and post-installation protection. 13.5 Updating core links both advisories and follow-up checks. Chapter 3 and chapter 13 summaries link to these additions.
Weekly reviews
2026 weekly index · This week’s core releases · Previous week’s 24 advisories