RC RANDOM CHAOS

Drupal patched a critical installer flaw Wednesday

Drupal patched CVE-2026-132165, a critical flaw letting anonymous attackers reach /core/install.php to reinstall the CMS. Block the installer and upgrade now.

· 3 min read
Drupal patched a critical installer flaw Wednesday

Drupal’s installer ships in every core install as /core/install.php, and under the right conditions an anonymous attacker can call it to reinstall the CMS on a site that is already running. That is CVE-2026-132165, the critical remote code execution flaw the Drupal Security Team patched on Wednesday. Per the advisory, under specific conditions an attacker can use the installer to attempt to reinstall Drupal, which can lead to site takeover or remote code execution.

The flaw was found by Anthropic’s OSS Scanner. Drupal rates it critical and says anonymous users can exploit it, which is the combination that makes it worth dropping other work for. There is a hardening detail in the advisory worth reading closely: some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. If your web server genuinely cannot write to or change permissions on that file, you have less exposure, but the team is not treating that as a substitute for the patch.

The fixed releases are Drupal 10.6.22, 11.3.22, and 11.4.13. Sites behind the paid Drupal Steward Web Application Firewall are already protected against the known attack vectors, according to Drupal, but the team still tells those admins to upgrade in case other vectors surface. If you cannot upgrade immediately, the stopgap is to block access to /core/install.php in your web server configuration or in the .htaccess file in the web root. That removes the reachable surface while you schedule the core update.

This matters more than a typical CMS advisory because of who runs Drupal. It is common in large organizations managing multi-site installations and large data structures: government entities, educational organizations, major research universities, and high-profile enterprise and media sites. An anonymous RCE in that population is a broad target, and Drupal’s own timeline suggests the window is short. In a Monday advance warning the team told admins to reserve time for the core update because exploits might be developed within hours or days, noting the vulnerabilities were rated critical and that at least one can be exploited by anonymous users.

The same release also addressed CVE-2026-132166, a moderately critical gadget chain vulnerability. This one is a different risk profile: an attacker with admin privileges can use it to gain remote code execution if the application deserializes untrusted data because of another security flaw. It needs both an existing admin foothold and a separate deserialization bug to chain against, so it is not the one driving the urgency. Patch it in the same pass, but CVE-2026-132165 is the reason to move now.

Drupal’s recent track record is the argument for taking the hours-or-days estimate seriously. In May the project confirmed attackers were actively exploiting an SQL injection flaw, CVE-2026-9082, in the database abstraction API, which could be used to escalate privileges, read sensitive data, or achieve remote code execution on unpatched servers. More recently Drupal warned that a critical access bypass in the Commerce Core module, CVE-2026-118539, was being abused in attacks. CISA has flagged five Drupal vulnerabilities as exploited in the wild since November 2021, two of which were also used in ransomware campaigns.

If you run Drupal, the order of operations is straightforward. Block /core/install.php at the web server now, since that takes seconds and closes the anonymous path. Then schedule the upgrade to 10.6.22, 11.3.22, or 11.4.13 rather than treating it as routine maintenance. Check whether your deployment keeps settings.php writable at runtime, because that permission is part of what decides how much the installer bug can do.

Share

Keep Reading

Latest on the Wire

Full wire →

New signal daily · RSS

Stay in the loop

New writing delivered when it's ready. No schedule, no spam.