Skip to content

Drupal patches a critical install.php RCE across every branch

SA-CORE-2026-017 lets an attacker abuse Drupal's own installer to force a reinstall and take over the site. A second, lower-severity gadget chain bug shipped in the same release.

Source: Drupal.org

Drupal shipped its pre-announced security release today, 18 November, inside the four-hour window the team had flagged two days earlier. SA-CORE-2026-017 is the headline fix: rated critical at 18 out of 25 and tracked as CVE-2026-132165, it lets an attacker abuse core’s install.php file to force Drupal through a reinstall under specific conditions, which can lead to a full site takeover or remote code execution.

The fix lands in 10.6.22, 11.3.22 and 11.4.13, covering every currently supported branch. Drupal’s own advisory notes the attack is partly blocked if the web server can’t write to settings.php, so file permissions matter as much as the code update. A second, moderately critical advisory, SA-CORE-2026-018, patches a “gadget chain” in the same release; it isn’t directly exploitable, but becomes a remote code execution path if a separate deserialisation bug exists elsewhere on the site.

composer require 'drupal/core:11.4.13' --update-with-dependencies

Why it matters: Drupal’s site count looks small next to WordPress, but it still concentrates in large organisations and government sites, the kind of install that tends to leave install.php reachable long after setup. If you run Drupal core, patch today rather than at the next maintenance window; the security team’s own warning was that exploits could appear within hours of release.

The caveat: there’s no confirmation of active exploitation yet, and the advisory doesn’t spell out every “specific condition” needed to trigger the installer path, so don’t treat the absence of a public PoC as safety.

Share

Related reading

More from The Wire

All briefs