The Drupal Security Team published a critical security update on November 18, 2026 for a flaw in Drupal core’s installer. Advisory SA-CORE-2026-017 says that under specific conditions an attacker can use install.php to try to reinstall a live site, which can lead to site takeover or remote code execution. The fixed releases are Drupal 11.4.13, 11.3.22 and 10.6.22.
What’s new
- The bug is tracked as CVE-2026-132165 and rated Critical, 18 out of 25 on Drupal’s risk scale. The advisory credits Anthropic’s OSS Scanner with finding it.
- Affected versions are everything below 10.6.22, 11.0.0 up to 11.3.22, and 11.4.0 up to 11.4.13.
- Drupal says some attack paths are blocked when the web server can’t write to settings.php or change its permissions. Sites behind the paid Drupal Steward firewall are covered against known attack routes but should still upgrade.
BleepingComputer reported on November 19 that Drupal expects working exploits could appear within hours or days. No attacks have been reported so far.
Who it affects
Any business running a Drupal 10 or 11 site that hasn’t installed this week’s release. Sites still on Drupal 11.2, 10.5 or older are in a worse spot, because those branches are past end of life and get no security fixes at all. If an agency or freelancer built your site years ago and nobody has touched it since, assume it needs attention.
WordPress, Shopify and Webflow sites aren’t affected by this one.
Our take
We’d patch this today, before exploit code shows up. Update to the fixed release for your branch, then block public access to /core/install.php in your web server config or .htaccess, which Drupal recommends for every site after setup anyway. While you’re in there, check that settings.php is read-only for the web server. If you’re stuck on an end-of-life branch, the upgrade can’t wait much longer, and that’s the moment to decide whether to move up or migrate to a platform your team can keep current.
Drupal has had a busy autumn, so see our earlier Drupal Commerce brief and this week’s nginx patch brief too. If you’d rather hand updates to someone else, our website maintenance service covers patching, and our website migration team can move an aging Drupal site.




