r/drupal • u/Horizon3ai • 3d ago
Drupal Core Installer Remote Code Execution Vulnerability (CVE-2026-132165): Site Takeover Risk, No Exploitation Confirmed, Patches Available
An attacker who can reach a Drupal site’s install.php may be able to take over the site and, potentially, execute code on the host. The flaw is CVE-2026-132165 in Drupal core’s installer. Drupal rates it Critical, 18/25 on its own risk scale, in advisory SA-CORE-2026-017. NVD has not yet published a CVSS v3.1 score. Drupal’s risk vector lists exploit maturity as Proof, and the advisory does not report exploitation in the wild.
How it works
Drupal core ships install.php, the script used to install a new site. Under specific conditions on an already-installed site, an attacker can invoke the installer and begin a reinstallation. The installation process writes configuration and runs site setup logic with the privileges of the web server. Driving it against a live site could therefore hand an attacker administrative control of the site or code execution on the host. Drupal states the flaw can be exploited by anonymous users, with no user interaction reported. Drupal rates confidentiality and integrity impact as total. Takeover and RCE are potential outcomes, not confirmed attacks.
Affected versions and configurations
- Drupal core before 10.6.22
- Drupal core 11.0.0–11.3.21
- Drupal core 11.4.0–11.4.12
- Drupal 8, Drupal 9, Drupal 10.5.x and below, and Drupal 11.2.x and below are end-of-life and receive no security coverage. Those sites must upgrade to a supported branch.
This isn’t a flaw in every Drupal site. Drupal states that some exploit paths are blocked if the web server cannot write to or change permissions on settings.php, the file that holds database credentials and site configuration. Internet exposure is not required: anyone who can reach a site’s install.php, including from an internal network or staging environment, can attempt the attack.
Remediation
Upgrade to Drupal 10.6.22, 11.3.22 or 11.4.13, released November 18, 2026. Drupal states that Drupal Steward customers are protected from known attack vectors but should still upgrade. Drupal also advises keeping installer access restricted after upgrading.
Recommended actions
- Patch to a fixed release, starting with internet-facing sites.
- Check every Drupal site, including staging and internal environments, for a reachable /core/install.php.
- Until you can patch, block public access to /core/install.php in the web server configuration or the .htaccess file in the site root.
- Ensure the web server cannot write to or change permissions on settings.php. This blocks some exploit paths but is a workaround, not a fix.
Horizon3 Attack Research team reversed this CVE. Learn more: https://horizon3.ai/attack-research/vulnerabilities/cve-2026-132165/
9
u/codefake 3d ago
good lord, i can't keep up
7
u/alphex https://www.drupal.org/u/alphex 3d ago •
I miss the days people took the time to write on their own.
1
u/pianomansam 3d ago
Yesterday’s thread https://www.reddit.com/r/drupal/s/aAWRX3HbaW
1
u/omgCHop 2d ago
Access to install.php should always be denied. I always wince when I find a Drupal site that hasn't locked that one down.