Skip to content
Critical Drupal Installer Flaw CVE-2026

Critical Drupal Installer Flaw CVE-2026

Cyberkendra •Sulochana • November 19, 2026

Drupal has patched a critical flaw in its core installer that can let an unauthenticated attacker reinstall a live Drupal site through install.php and take it over, with remote code execution on the server possible in some configurations.

The bug, tracked as CVE-2026-132165 , affects every supported Drupal core branch before 10.6.22, 11.3.22, and 11.4.13. Drupal rates it Critical at 18 out of 25 on its own risk scale, and the National Vulnerability Database had not published a CVSS score as of November 20.

The Drupal Security Team disclosed the issue in advisory SA-CORE-2026-017 on Wednesday, November 18, alongside fixed releases. Drupal’s own risk vector marks a proof of concept as existing, though no exploit code has been published.

As of November 20, fixes are available for all three supported branches, and neither Drupal nor Horizon3 ai , which published an analysis on November 19, reports exploitation in the wild.

How the Drupal Installer Flaw Works

Drupal core ships install.php (served at /core/install.php ), the script that sets up a new site. On a site that is already installed, the installer should refuse to run. Under specific conditions, CVE-2026-132165 lets an attacker invoke it anyway and start a reinstall.

A Drupal reinstall writes configuration and runs setup logic with the web server’s privileges, so an attacker who drives it can end up with administrative control of the site, and from there, code execution on the host, according to Horizon3.ai’s analysis. Drupal’s advisory describes the result as site takeover or remote code execution.

The attack needs no account and no user interaction, only network access to install.php . Horizon3.ai notes that the endpoint does not have to face the internet, so internal, staging and development hosts reachable by an attacker count too.

Why Drupal Rates CVE-2026-132165 Critical, Not Highly Critical

Drupal’s risk vector for CVE-2026-132165 is AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon. In plain terms: no authentication is needed, a successful attacker can read all non-public data and change or delete anything, and a proof of concept exists.

Two factors hold the score at 18 rather than the 20-plus “Highly critical” band. Drupal says exploitation requires a complex, multi-step process, and only uncommon module configurations are exploitable. Neither Drupal nor Horizon3.ai has said which modules or configurations those are.

The advisory also does not say which Drupal version introduced the bug, and no fix commit has been publicly tied to it.

Which Drupal Versions Are Affected and Fixed

According to SA-CORE-2026-017, Drupal core versions before 10.6.22, from 11.0.0 before 11.3.22, and from 11.4.0 before 11.4.13 are vulnerable. Sites on Drupal 11.4.x should update to 11.4.13, sites on 11.3.x to 11.3.22, and sites on 10.6.x to 10.6.22.

Drupal 11.2.x and below, Drupal 10.5.x and below, and Drupal 8 and 9 are end-of-life and will not receive a fix. Sites on those branches have to move to a supported minor release to get patched.

Drupal credits the discovery to Anthropic’s OSS Scanner, which tracked the issue as ANT-2026-GMRPK0BU. The reporters listed on the advisory are Lee Rowlands of the Drupal Security Team, Pamela Barone, Scott Euser, Stephan Zeidler, and Tyler Nighswander, and the fix was built by more than a dozen Security Team members, including Alex Pott, Benji Fisher, Drew Webber, and Jess (xjm).

Is CVE-2026-132165 Being Exploited?

As of November 20, there are no reports of CVE-2026-132165 being exploited in attacks. Drupal’s advisory does not report in-the-wild use, Horizon3.ai reported none as of November 19, and the flaw is not listed in CISA’s Known Exploited Vulnerabilities catalog.

Drupal’s “E:Proof” rating means a working proof of concept exists, but the advisory withholds exploit details, and no public exploit code has surfaced. Neither source has released indicators of compromise, log signatures, or counts of exposed sites.

Recent Drupal core bugs have been weaponised quickly once details leaked. CISA added CVE-2026-9082 , an anonymous SQL injection in Drupal core disclosed on May 20, to the KEV catalog after exploitation attempts were detected within days of the advisory.

What Drupal Admins Should Do Now

The only fix for CVE-2026-132165 is updating Drupal core to 10.6.22, 11.3.22, or 11.4.13. On Composer-managed sites, composer show drupal/core or drush status shows the installed version, and the update is applied with Composer followed by drush updatedb and a cache rebuild.

After upgrading, Drupal recommends locking down the installer using its guide to securing install.php . Horizon3.ai advises blocking public access to /core/install.php in the web server configuration or the site root .htaccess , and keeping that restriction in place permanently.

Drupal also says some exploit paths are blocked if the web server cannot write to, or change the permissions of, settings.php . Admins who cannot upgrade immediately should apply the installer-securing steps and tighten settings.php permissions, but both Drupal and Horizon3.ai stress these are workarounds, not fixes.

Sites enrolled in Drupal Steward, Drupal’s web application firewall service, are already protected against known attack vectors, according to the advisory. Drupal still tells Steward users to upgrade soon in case new vectors are found.

Join the conversation. Ask questions, solutions, and help others.

Be the first to start the discussion!

Extracted Entities