The Drupal Security Team disclosed a critical vulnerability (CVE-2026-132165) in install.php, the installer that ships with Drupal core, on November 18, 2026 (local time), and released fixed versions 10.6.22, 11.3.22 and 11.4.13. Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. That can lead to a site takeover or remote code execution (RCE), meaning an outsider could run arbitrary code on the server.

Rated Critical, 18 out of 25

In security advisory SA-CORE-2026-017, the team rated the flaw Critical, with a score of 18 out of 25. The breakdown lists the access required as "None (all/anonymous users)" and carries the "Proof" label, indicating that a proof of concept exists.

At the same time, the rating notes that the attack is complex, with many dependencies, and that only uncommon module configurations are exploitable. The advisory says some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. As of this writing, the team has not detailed the "specific conditions" required for exploitation.

The advisory credits Anthropic's "OSS Scanner" with discovering the vulnerability.

Fixes for Three Branches; 11.2 and Earlier and 10.5 and Earlier Are Unsupported

Affected versions are those before 10.6.22, from 11.0.0 up to but not including 11.3.22, and from 11.4.0 up to but not including 11.4.13. The action for each branch is as follows.

BranchAction
Drupal 11.4.xUpdate to 11.4.13
Drupal 11.3.xUpdate to 11.3.22
Drupal 10.6.xUpdate to 10.6.22
Drupal 11.2.x and earlier / 10.5.x and earlier / 8 / 9End of life (no security fixes)

The same releases also fix a second issue, SA-CORE-2026-018 (CVE-2026-132166, rated Moderately critical). It is a "gadget chain," a chain of methods that could serve as a stepping stone to RCE if a separate insecure deserialization flaw (unsafe restoring of data received from outside) exists on the site. The team says this issue is not directly exploitable on its own.

Advance Notice Warned Exploits Could Appear Within Hours or Days

On November 16, the team published an advance notice, PSA-2026-11-16, announcing a security release for all supported branches on November 18 between 17:00 and 21:00 UTC (2:00 to 6:00 a.m. on November 19, Japan time / JST). The notice asked administrators to reserve time for updates, warning that exploits might be developed within hours or days.

The notice also said at least one of the vulnerabilities can be exploited by anonymous users and that more than one configuration is affected, urging site owners not to assume their sites are safe. Development releases 12.0.0-beta3 and 11.5.0-beta1 are also affected, and new beta or release candidate versions will follow. Sites using Drupal Steward, a paid protection service, are already protected from known attack vectors, according to the notice.

Site Administrators Need to Update and Block install.php

In addition to upgrading, the team recommends securing the installer after installation. Drupal's official documentation, Securing the installer (install.php), explains that /core/install.php is needed only once, to install a site, and that access to it should be blocked afterward.

The recommended method is to deny access to that path in the Apache or Nginx web server configuration. For shared hosting and other setups where the server configuration cannot be changed, the documentation also describes blocking it with .htaccess or deleting the file through Composer scripts. For Nginx, it cautions against using an exact-match rule, because that would not block paths such as /core/install.php/foo.

The documentation also notes that update.php, used for updates, is a separate script and should not be blocked by accident with an overly broad rule. After making the change, administrators should confirm that requests to install.php end in a 403 or 404 response, and that the site and the update process still work normally.

Our Take

By announcing the release time in advance and updating its mitigation guide alongside the advisory, the Drupal team made it relatively easy for administrators to prepare. The fact that an AI-based vulnerability scanner is credited with the discovery also appears to be an example of how the pool of contributors checking open source software is widening.

However, install.php is a file that is easy to forget once a site is up, and it may still be publicly reachable on many sites. Sites that continue to run the unsupported 11.2 and earlier or 10.5 and earlier branches cannot get a fix and will have to rely on mitigations such as blocking access.

That said, the required work is mostly an update plus a web server configuration change, and the steps are officially documented. Given the notice's warning that exploits could appear quickly, this is an issue that sites of every size should address soon.

Summary

Drupal has released 10.6.22, 11.3.22 and 11.4.13, fixing a critical vulnerability that could allow attackers to abuse the installer to take over a site. Administrators running Drupal sites need to update to the fixed versions and block access to install.php. Development releases are also affected, and the team plans to provide new beta and release candidate versions later.