Drupal fixes critical installer flaw that allows site takeover

Anonymous attackers can abuse install.php to reinstall Drupal and gain code execution; Drupal warns exploits may follow within hours and urges blocking the installer.

SecurityPublished
What happened
Drupal released fixes on 18 November for a critical remote code execution flaw in its core installer, tracked as CVE-2026-132165.
What’s new
An attacker can use install.php to try reinstalling an existing Drupal site, which can lead to takeover or code execution.
Why it matters
Drupal says exploits could appear within hours or days, and earlier Drupal flaws have been exploited in real attacks.

The Drupal Security Team published advisory SA-CORE-2026-017 on 18 November, rating as critical a remote code execution flaw in Drupal core's installer, install.php. According to the advisory, under certain conditions an attacker can use the installer to attempt a fresh install over an existing site, which can result in site takeover or remote code execution. BleepingComputer reports that anonymous users can exploit the bug, tracked as CVE-2026-132165. The advisory credits its discovery to Anthropic's OSS Scanner.

Patches and exposure

According to BleepingComputer, the fixed releases are Drupal 10.6.22, 11.3.22 and 11.4.13. Drupal says sites using its paid Drupal Steward firewall service are already shielded from known attack paths but should still upgrade soon, in case new paths turn up. The advisory also notes that some exploit routes are blocked when the web server cannot write to settings.php or change its permissions.

In an advance notice on 16 November, the Drupal Security Team told administrators to set aside time for updates because exploits might be developed within hours or days, BleepingComputer reports. The same release fixed a second, moderately critical gadget chain flaw (CVE-2026-132166) that requires admin privileges and a separate flaw that lets the site deserialize untrusted data.

Blocking the installer correctly

Beyond upgrading, Drupal recommends cutting off access to /core/install.php once a site is installed. Its guide offers three methods: a web server rule (its preferred option), a .htaccess rule on Apache, or deleting the file. Several pitfalls are spelled out. On Apache, the Location directive belongs in the server configuration; placed in .htaccess it breaks the whole site with a 500 error. On Nginx, Drupal advises a prefix match using ^~, warning that an exact-match rule can be bypassed on setups that pass paths containing .php/ to PHP. On Composer-based sites, .htaccess is rewritten whenever the scaffold step runs, and a deleted install.php is restored on each install or update, so manual changes vanish.

The guide says blocking the installer does not affect update.php, and that Drush's site:install command does not rely on install.php. Drupal suggests checking with curl that the installer returns 403 or 404.

Track record

BleepingComputer notes that Drupal confirmed active exploitation of an SQL injection flaw (CVE-2026-9082) in May and later of a Commerce Core access bypass (CVE-2026-118539). BleepingComputer also reports that CISA has listed five Drupal vulnerabilities as exploited since November 2021, two of them in ransomware attacks.