Drupal core flaw can let attackers reinstall sites to take them over
- Affected
- Drupal core before
10.6.22,11.0.0through11.3.21and11.4.0through11.4.12, Drupal says. All versions and fixes
- Vendor
- Drupal
A flaw in Drupal core’s installer, install.php, can let an attacker reinstall Drupal on a running site under specific conditions, leading to a site takeover or code execution, Drupal says. Drupal rates it critical, 18 out of 25 on its own scale, and its rating shows no login is needed. Drupal 11.4.13, 11.3.22 and 10.6.22 fix it, and no attacks have been reported.
Drupal ships install.php to set up a new site. Under conditions Drupal hasn’t detailed, an attacker can use it to try to reinstall Drupal over an existing site. Some attack paths fail when the web server can’t write to settings.php or change its permissions, Drupal says. Its rating marks the attack as complex and the vulnerable setups as uncommon, but puts the impact on confidentiality and integrity at the highest level.
Drupal 10 before 10.6.22 and Drupal 11 before 11.3.22 or 11.4.13 are affected. Drupal 11.2 and 10.5 and older branches, and Drupal 8 and 9, are end of life and get no fix. Sites that use Drupal Steward, Drupal’s protection service, are already protected from the known attack vectors, Drupal says, though they should still upgrade in case others turn up.
The same releases fix a second flaw, a gadget chain that Drupal rates moderately critical. It isn’t directly exploitable, but it could help an attacker run code if another flaw lets them pass untrusted data to PHP’s unserialize() function.
Drupal credits Anthropic’s OSS Scanner with finding the installer flaw. Drupal hasn’t described the conditions that make a site vulnerable, and the CVE record its advisory lists for the flaw hadn’t been published as of Nov 19.
- Vendor
- Drupal
What to do
4 steps
Affected and fixed versions
| Product | Affected | Fixed |
|---|---|---|
| Drupal 11.4 | 11.4.0 through 11.4.12 | 11.4.13 |
| Drupal 11.0 to 11.3 | 11.0.0 through 11.3.21 | 11.3.22, since 11.2 and older are end of life |
| Drupal 10 | Before 10.6.22 | 10.6.22, since 10.5 and older are end of life |
- Product
- Drupal 11.4
- Affected
11.4.0through11.4.12- Fixed
11.4.13
- Product
- Drupal 11.0 to 11.3
- Affected
11.0.0through11.3.21- Fixed
11.3.22, since 11.2 and older are end of life
- Product
- Drupal 10
- Affected
- Before
10.6.22 - Fixed
10.6.22, since 10.5 and older are end of life
Timeline
- Nov 18Drupal publishes the advisory and the fixed releases.
Sources
- Drupal advisory SA-CORE-2026-017Primary source drupal.org
- Drupal advisory SA-CORE-2026-018Primary source drupal.org