Skip to content
eastbaycyber

Disclosure: this page contains affiliate links. East Bay Cyber may earn a commission if you buy through them, at no extra cost to you. That never changes how we rank products. Editorial policy.

Drupal reports live-site exploitation of critical install.php RCE flaw

Breaking news 7 min read
EC
East Bay Cyber Editorial Team Updated Developing story
Built from the vendor or authority notice plus independent reporting; unconfirmed claims are labeled as reported. Human-reviewed after publishing.

TL;DR - Update: Drupal now says the vulnerability was exploited on live sites as early as 19 November 2026 at 19:00 UTC. - Drupal fixed a highly critical remote code execution vulnerability in the core installer, tracked as CVE-2026-132165. - Under specific conditions, an attacker can use /core/install.php to attempt to reinstall Drupal, which can lead to site takeover or remote code execution. - Fixed releases are Drupal 11.4.13, 11.3.22, and 10.6.22. - Drupal recommends securing the installer after installation, including for sites that update.

What happened#

Drupal disclosed a highly critical vulnerability in its core installer on 18 November 2026. The issue affects the install.php file used to install Drupal core. Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal, potentially leading to site takeover or remote code execution, according to Drupal’s security advisory.

The advisory identifies the issue as CVE-2026-132165 and gives it a security risk rating of Highly critical, with a score of 20 ∕ 25. Drupal says some exploit paths are mitigated when the web server cannot write to or change permissions on settings.php.

Drupal’s affected ranges are below 10.6.22, Drupal 11.0.0 through versions before 11.3.22, and Drupal 11.4.0 through versions before 11.4.13. Drupal says the vulnerability was discovered by Anthropic’s OSS Scanner.

The advisory now includes an update stating that the Drupal Security Team received a report that the vulnerability was exploited on live sites as early as 2026-11-19 19:00 UTC. The advisory does not provide further details about those incidents.

Drupal released fixes for supported branches. The Drupal 11.4.13 release page says sites on Drupal 11.4.x should update to Drupal 11.4.13, sites on Drupal 11.3.x should update to Drupal 11.3.22, and sites on Drupal 10.6.x should update to Drupal 10.6.22.

The release notes also say that, during installation, Drupal previously attempted to automatically fix permissions when settings.php was not writable. The installer will instead present an error message in that situation. Drupal says this change affects new installations and does not affect existing sites.

Drupal’s installer guidance says the file remains on the site after installation and should be blocked. The documentation describes blocking it in web server configuration, blocking it through .htaccess, or removing the file. Blocking install.php does not affect updates because update.php is a separate script: Drupal’s installer security guidance.

BleepingComputer previously reported that Drupal warned exploits might be developed within hours or days. That warning is now accompanied by Drupal’s report of exploitation on live sites.

Are you affected#

You may be affected if your site runs an affected Drupal core version and the installer remains reachable. Drupal’s affected versions are:

  • Below 10.6.22.
  • Drupal 11.0.0 before 11.3.22.
  • Drupal 11.4.0 before 11.4.13.

Drupal 11.2.x and below, as well as Drupal 10.5.x and below, are end-of-life and do not receive security coverage. Drupal 8 and Drupal 9 have also reached end-of-life, according to the Drupal advisory.

The installer is located at /core/install.php. Drupal’s documentation says it is needed to install a new site, including adding a new site to a multisite setup, but should be blocked after installation. The documentation also says blocking install.php does not affect updates because update.php is a separate script.

The installer should be reviewed across production, staging, development, and multisite deployments. Sites that cannot update immediately should follow Drupal’s instructions for blocking the installer.

Drupal says sites using Drupal Steward are already protected from known attack vectors, but should still upgrade in case additional attack vectors are discovered. That protection does not change the affected version ranges or the need to review the installer’s exposure.

What is confirmed and what is reported#

Claim Source Status
Drupal core has a highly critical remote code execution vulnerability involving install.php. Drupal security advisory Confirmed
The vulnerability is CVE-2026-132165. Drupal security advisory Confirmed
Under specific conditions, an attacker can attempt to reinstall Drupal, potentially causing site takeover or remote code execution. Drupal security advisory Confirmed
Drupal reports that the vulnerability was exploited on live sites as early as 2026-11-19 19:00 UTC. Drupal security advisory Confirmed
The fixed releases are 11.4.13, 11.3.22, and 10.6.22. Drupal 11.4.13 release page, Drupal security advisory Confirmed
Exploits might be developed within hours or days. BleepingComputer Reported
The vulnerability has an existing proof-of-concept exploit and exploitation is complex. The Hacker News Reported
The advisory previously recorded no attacks. Drupal’s current advisory now reports exploitation on live sites as early as 2026-11-19 19:00 UTC. The Hacker News, Drupal security advisory Reported

What defenders should do now#

  1. Identify Drupal core versions across production, staging, development, and multisite installations. Review whether /core/install.php is reachable.

  2. Update supported branches to the releases specified by Drupal: Drupal 11.4.x to 11.4.13, Drupal 11.3.x to 11.3.22, and Drupal 10.6.x to 10.6.22. Drupal’s release page urges sites to update immediately after reading the security announcements and release notes: Drupal 11.4.13.

  3. Secure the installer after installation. Drupal recommends blocking access to /core/install.php in the web server configuration. The documentation also describes an Apache .htaccess option and removing the file.

  4. If using Composer, account for file replacement. Drupal says .htaccess is a scaffold file and hand-added lines can be lost when the scaffold step runs, including during a plain composer install. The documentation describes using a separate additions file and Composer configuration to preserve the change.

  5. If removing core/install.php, account for Composer restoring it during installs or core updates. Drupal documents Composer scripts for removing it again, and notes that this does not work when deployment runs composer install --no-scripts.

  6. Check that the installer block works. Drupal’s documentation says requests to /core/install.php, /install.php, and /core/install.php/foo should end with a 403 or 404 response. It also says to confirm that the site continues to work normally and that database updates can still run.

  7. Review older deployments separately. Drupal says Drupal 11.2.x and below, Drupal 10.5.x and below, Drupal 8, and Drupal 9 do not receive security coverage. The available advisory does not publish a fix for those branches.

  8. Because Drupal reports exploitation on live sites as early as 2026-11-19 19:00 UTC, review relevant web server, application, and administrative logs for suspicious requests to the installer and investigate affected systems according to the organization’s incident response procedures. The advisory does not publish indicators or further incident details.

This advisory is informational and is updated as vendors publish details. Confirm versions and actions against Drupal’s own guidance for your environment.

This advisory is informational and is updated as vendors publish details. Confirm versions and actions against the vendor’s own guidance for your environment.

Sources

Last verified: 2026-11-21

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.