Skip to content
TrustList
Security advisories

Drupal core fixes critical installer takeover flaw in SA-CORE-2026-017

Editorial

By TrustList Editorial

Drupal published SA-CORE-2026-017, a critical flaw that can let an attacker use install.php to reinstall a site and take it over, and SA-CORE-2026-018, a gadget chain, on 18 November 2026; releases 11.4.13, 11.3.22 and 10.6.22 came out that day.

About Drupal core fixes critical installer takeover flaw in SA-CORE-2026-017

Drupal core fixes critical installer takeover flaw in SA-CORE-2026-017

18 November 2026: The Drupal security team has published two core advisories. SA-CORE-2026-017 is rated critical: under specific conditions an attacker can use the installer to try to reinstall Drupal, which "can lead to a site takeover or remote code execution." SA-CORE-2026-018 is rated moderately critical and describes a gadget chain that becomes dangerous only alongside another flaw. New releases of drupal/core, 11.4.13, 11.3.22 and 10.6.22, appeared in Drupal's package registry alongside them.

Not yet independently verified. Advisory titles, risk scores, CVE numbers and the quoted descriptions come from the Drupal.org security listing and the core security feed of 18 November 2026, and the public service announcement of 16 November. The affected ranges and fixed versions are from the advisory text in the security feed and match the drupal/core releases tagged on 18 November; the individual advisory pages answered with a browser check and were not read. CVE.org had not yet published records for the two CVE numbers, so there is no CVSS score. We will update this when it can be confirmed, and remove this note.

The installer flaw

Drupal ships an install.php file that sets up a new site. The advisory, tracked as CVE-2026-132165, says that under specific conditions an attacker can use that file against an existing site. Drupal scores the risk at 18 out of 25. Its scoring marks the attack as complex and the affected configuration as uncommon, but the impact as total loss of confidentiality and integrity, and it records that proof-of-concept exploit code exists.

The security team had warned of the release two days earlier. Its public service announcement of 16 November said fixes for all supported branches would ship on 18 November between 17:00 and 21:00 UTC, that at least one flaw could be exploited by anonymous users, and that exploits "might be developed within hours or days". Sites covered by the Drupal Steward programme are protected against the known attack paths, according to the announcement, but updating remains the fix.

The pattern is familiar: TYPO3 fixed a similar installer takeover flaw on 17 November, and exposed installer files are an easy thing for attackers to look for.

The gadget chain

SA-CORE-2026-018, CVE-2026-132166, scores 14 out of 25. The advisory says Drupal core contains a chain of methods that could be exploited when an insecure deserialization vulnerability exists elsewhere on the site, for example in a contributed module, and that "this issue is not directly exploitable." Fixing it removes a building block that turns other bugs into code execution.

What site owners should do

Update drupal/core to the release for your branch: 11.4.13 for 11.4, 11.3.22 for 11.3 and 10.6.22 for 10.6, as tagged on 18 November. Branches 11.2 and older, 10.5 and older, and Drupal 8 and 9 are end of life and get no fix. With Composer, run composer update for drupal/core and its recommended packages, then run database updates and clear caches.

The advisory says some attack paths are blocked if the web server cannot write to settings.php or change its permissions, and it recommends securing the installer after installation. Whatever your version, make sure install.php cannot be reached from the internet on a live site. Blocking the core/install.php path at the web server or load balancer is a simple safeguard against the critical flaw and any repeat of it. Check that settings.php is read-only and that the database credentials in it cannot be overwritten by the web server user.

Sites on an end-of-life branch should move to a supported one or check with their extended support vendor. Agencies running many sites should prioritise those on shared or older hosting, where installer files are most often left exposed.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in