News Vulnerabilities & Zero-Days
Drupal Patches Critical Installer Flaw That Can Let Anonymous Attackers Reinstall a Site
Drupal has fixed CVE-2026-132165, a critical core flaw in which an attacker can, under specific conditions, use the installer to attempt to reinstall a running site. No authentication is required, though Drupal rates the attack as complex and limited to uncommon configurations.

Key takeaways
- CVE-2026-132165 lets an attacker, under specific conditions, use Drupal's installer to attempt a reinstall, leading to site takeover or code execution.
- No authentication is required and Drupal records that a proof of concept exists, but it rates the attack as complex and limited to uncommon configurations.
- The advisory does not report exploitation in the wild.
- Fixed releases exist for supported branches only. End-of-life branches get no fix.
- The advisory credits discovery to Anthropic's OSS Scanner.
Drupal has published SA-CORE-2026-017 for CVE-2026-132165, a critical remote code execution issue in Drupal core. The advisory says that under specific conditions an attacker can use the installer to attempt to reinstall Drupal on a site, which can lead to site takeover or remote code execution.
How serious is it #
Read the rating carefully. Drupal's risk string rates the flaw Critical and records that no authentication is needed: anonymous users can attempt it. It also records that a proof of concept exists. In the same string, Drupal rates access complexity as Complex and says only uncommon module configurations are exploitable. So this is unauthenticated and critical, but it is not a claim that every Drupal site can be taken over.
The advisory does not say exploitation has been observed. BleepingComputer quotes an advance warning from the Drupal Security Team that "exploits might be developed within hours or days".
Fixes and mitigations #
Fixed releases are available for all supported branches of Drupal core, and the advisory lists the exact affected and fixed releases. It directs sites to upgrade and to follow Drupal's instructions for securing the installer.
Other points from the advisory:
- Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php.
- Sites that use Drupal Steward are already protected from known attack vectors, but should still upgrade in the near future in case additional vectors are discovered.
- End-of-life branches are listed as such and get no fix. Teams on those need an upgrade plan, not a patch.
BleepingComputer reports an interim mitigation: block access to /core/install.php in the web server configuration or .htaccess. It also reports a second, moderately critical gadget-chain flaw, CVE-2026-132166, patched at the same time and exploitable by attackers with admin privileges.
Credit #
The advisory's credit line reads: "Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-GMRPK0BU."
What to do #
- Upgrade to the fixed release for your branch.
- Confirm install.php is not reachable on production, and that the web server cannot modify settings.php.
- If you are on an end-of-life branch, schedule the move to a supported one now.
Sources
- Drupal core - Critical - Remote code execution - SA-CORE-2026-017 | Drupal.org, Drupal Security Team
- Drupal patches critical RCE flaw, warns exploits may surface quickly, BleepingComputer
Questions this raises
- Is CVE-2026-132165 being exploited?
- The Drupal advisory does not state that exploitation has been observed. Drupal's risk string records that a proof of concept exists, and BleepingComputer quotes a Drupal Security Team advance warning that exploits might be developed within hours or days.
- Are all Drupal sites vulnerable?
- Not according to Drupal's own rating. The flaw needs no authentication, but Drupal rates access complexity as Complex and says only uncommon module configurations are exploitable. The advisory lists the affected release ranges.
- What can I do if I cannot upgrade right away?
- The advisory says some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php, and that Drupal Steward sites are protected from known attack vectors. BleepingComputer reports blocking access to /core/install.php in the web server configuration or .htaccess as a mitigation.
- Who found the vulnerability?
- The advisory's credit line says it was discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-GMRPK0BU.