Threat Intelligence

Drupal Fixes Critical Installer Flaw That Could Let Anyone Without a Login Try to Take Over a Site

The Hacker News · 20 Nov 2026
Key Takeaway If your business runs Drupal, update to a fixed release now and block access to /core/install.php, and plan a migration if you are on an end-of-life version.

The Drupal Security Team has released fixes for a critical vulnerability in Drupal core, tracked as CVE-2026-132165. Under specific conditions, someone with no login credentials can use the built-in installer to try to reinstall a site. That can lead to a site takeover or remote code execution. The project rates the vulnerable configurations as uncommon, and scores the flaw 18 out of 25 on its risk scale.

The installer is the file /core/install.php, which ships in every copy of Drupal core and stays on the site after setup. Core's default .htaccess rules do not block requests to it, so each site has to block it themselves. The advisory reports no attacks, and rates exploitation as complex, but it records that a proof-of-concept exploit exists. Some exploit paths are blocked where the web server cannot write to or change permissions on settings.php. The team warned in advance that exploits could appear within hours or days.

Affected versions are every release below 10.6.22, Drupal 11 from 11.0.0 before 11.3.22, and 11.4.0 before 11.4.13. Fixed releases are available for all supported branches. The team recommends blocking the installer even after updating. Sites that cannot update yet can use the project's installer guidance: a deny rule in the web server configuration, an .htaccess rule, or removing the file and keeping it removed with Composer scripts. Drupal Steward customers are protected from known attack vectors but should still update.

Older branches are a concern. Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end-of-life and get no fix. In the week of November 8, about 29 percent of sites reporting usage data were on end-of-life branches. The flaw was found by Anthropic's OSS Scanner, an automated service, and it is the second critical remote code execution flaw fixed in Drupal core in two months.

Why it matters

The installer file is present on every Drupal site by default and the default rules do not block it, so the control that was assumed to protect a finished site was never there. Sites on end-of-life branches face the sharpest decision, because no patch is coming and blocking the installer becomes their only mitigation. With a public proof-of-concept and the team's warning of exploits within hours or days, the low rating for exploit complexity should not justify delay.

What to do

  • Update to Drupal 10.6.22, 11.3.22, 11.4.13 or later, depending on your branch.
  • Block requests to /core/install.php with a web server deny rule or .htaccess rule, even after updating.
  • Remove the install.php file and keep it removed using Composer scripts if you cannot update yet.
  • Check whether your web server can write to or change permissions on settings.php, and restrict it where possible.
Drupal CVE-2026-132165 remote code execution patching end-of-life software

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.