Drupal patches critical installer flaw allowing unauthenticated site takeover
Drupal has released urgent security updates to fix a critical vulnerability in its core installer that could allow attackers to reinstall and take over sites without credentials.
The Drupal Security Team has issued critical patches for multiple versions of its content management system to address a severe vulnerability tracked as CVE-2026-132165. Disclosed on November 18, 2026, this flaw allows unauthenticated attackers to potentially execute remote code or take full control of a site by exploiting the built-in installer. Fixed releases are now available for all supported branches, requiring immediate attention from self-hosting teams.
What happened
The vulnerability resides in the Drupal core installer, specifically the file /core/install.php, which remains on the server after the initial setup is complete. Under specific conditions, an attacker can trigger this installer to attempt a reinstallation of the site. If successful, this process can lead to a complete site takeover or remote code execution, granting the attacker full administrative privileges. The Drupal Security Team rated the risk at 18 out of 25, classifying it as critical, although they noted that vulnerable configurations are relatively uncommon.
While no active attacks have been reported in the security advisory, the team warned that exploitation complexity is moderate and a proof-of-concept exploit already exists. They had issued an advance notice earlier in the week, urging site owners to prepare for updates because exploits could be developed within hours or days of disclosure. The default .htaccess rules in Drupal core do not block requests to the installer file, meaning protection relies on individual site configurations or manual intervention.
Key details
- Affected versions: All Drupal 10 releases below 10.6.22, Drupal 11 releases from 11.0.0 before 11.3.22, and Drupal 11 releases from 11.4.0 before 11.4.13.
- Fixed versions: Update to 10.6.22, 11.3.22, or 11.4.13 depending on your branch.
- End-of-life branches: Drupal 8, 9, 10.5.x and earlier, and 11.2.x and earlier receive no fix.
- Mitigation: Block access to
/core/install.phpvia web server configuration,.htaccessrules, or by removing the file entirely. - Discovery: The flaw was identified by Anthropic's OSS Scanner, an automated tool launched in October 2026.
- Support changes: Drupal is reducing security coverage for core minor versions from 12 months to 8 months starting in 2027 due to increased report volumes.
Background
For those managing self-hosted infrastructure, understanding the role of the installer file is crucial. During the initial setup of a Drupal site, the installer configures the database and creates the settings.php file. Typically, this file should be inaccessible or removed after installation to prevent unauthorized reconfiguration. However, Drupal leaves it in place by default, relying on server-level rules to block external access. If these rules are missing or misconfigured, the installer becomes a potential entry point for attackers.
This incident highlights a growing trend in open-source security: the use of automated AI-driven scanners to find vulnerabilities. Anthropic's OSS Scanner automatically analyzes opt-in projects and reports findings directly to maintainers. While this accelerates discovery, it also increases the workload for volunteer security teams. The Drupal team recently announced that the surge in AI-generated reports is unsustainable under current funding models, leading to shortened support windows for older versions.
Why it matters
For IT leads and DevOps engineers running Drupal instances, this vulnerability underscores the risks of default configurations. Even if your site is not currently targeted, the existence of a proof-of-concept exploit means that automated bots may soon begin scanning for unprotected installer files. Since the attack requires no login credentials, any exposed instance is at risk of immediate compromise. This is particularly concerning given that approximately 29 percent of sites reporting usage data were running end-of-life branches as of early November 2026.
Furthermore, the upcoming reduction in support coverage means that staying current with updates is more critical than ever. With security windows shrinking from 12 to 8 months starting in 2027, teams must streamline their patch management processes. Delaying updates not only exposes systems to known flaws like CVE-2026-132165 but also increases the likelihood of encountering unsupported software that will not receive future fixes. This shift places a higher burden on internal teams to monitor version lifecycles and plan upgrades proactively.
What you can do
- Update immediately: Upgrade to Drupal 10.6.22, 11.3.22, or 11.4.13 depending on your current version.
- Block the installer: Add a deny rule in your web server configuration or
.htaccessfile to block access to/core/install.php. - Remove the file: If possible, delete
/core/install.phpand use Composer scripts to ensure it does not return during future updates. - Check end-of-life status: Verify if your site is running an unsupported branch (e.g., Drupal 8, 9, or older 10/11 minors) and plan a migration.
- Review permissions: Ensure the web server cannot write to or change permissions on
settings.phpto block certain exploit paths. - Monitor for alerts: Set up monitoring for your Drupal instances to detect unusual activity or failed installation attempts.



