Drupal's installer can be abused to take over sites

Published

Drupal has fixed a critical bug in the setup script that ships with every copy of its core software. Under specific conditions, an attacker can use the installer to try to reinstall Drupal on a live site, which the project says can lead to a site takeover or remote code execution, meaning the attacker runs their own code on the server.

The Drupal Security Team's advisory, SA-CORE-2026-017, published on November 18, rates the flaw (CVE-2026-132165) Critical, 18 out of 25 on Drupal's own risk scale. The advisory does not publish a CVSS score. Its risk string lists the exploit status as "Proof", the project's label for a known proof of concept rather than a purely theoretical issue, and rates attack complexity as complex. Hong Kong's HKCERT relayed the fixes in a bulletin the following day.

Who found it, and which sites are exposed

Drupal credits the discovery to Anthropic's OSS Scanner and lists Lee Rowlands, Pamela Barone, Scott Euser, Stephan Zeidler and Tyler Nighswander as reporters. Affected releases are every Drupal version before 10.6.22, 11.0.0 up to 11.3.22, and 11.4.0 up to 11.4.13.

The advisory says some exploit paths are blunted if the web server cannot write to, or change permissions on, the site's settings.php file. Sites using the paid Drupal Steward service are already protected against known attack vectors, though the team still advises upgrading soon in case others turn up. Drupal has not described exploitation in the wild.

A second fix closes off a gadget chain

The same release ships SA-CORE-2026-018 (CVE-2026-132166), rated Moderately critical, 14 out of 25, again with no CVSS published. It removes a "gadget chain", a set of existing methods in core that an attacker could string together to run code if some other bug on the site lets them feed untrusted data to PHP's unserialize(). Drupal stresses that the issue is not directly exploitable on its own. It was reported by Drew Webber of the Drupal Security Team.

This is the second critical Drupal core fix in under a month, after the Field UI flaw patched in October.

Update to 10.6.22, 11.3.22 or 11.4.13 and lock the installer

Drupal 11.2.x and older, 10.5.x and older, and all of Drupal 8 and 9 are end-of-life and get no fix. Sites still on those branches have no patch to apply, which makes this the kind of bug that turns a long-postponed upgrade into an urgent one.

This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.

Read the full analysis on IntelFusions