Unbiased headlines. Facts, not spin.
Unbiased Headlines is an independently owned news organization. We bring you the facts, not opinions, written fresh from 110+ named sources. Sources linked so you can verify it yourself.
Drupal Patches Critical Installer Flaw Letting Anonymous Users Reinstall Sites, No Exploitation Reported

Since the Drupal Security Team's Monday, Nov. 16 advance warning to reserve time for a core update, the patch has landed: on Wednesday, Nov. 18, Drupal shipped fixes for a critical remote code execution flaw in its installer.
The bug is tracked as CVE-2026-132165 and published as advisory SA-CORE-2026-017. It is rated critical, 18 out of 25 on Drupal's scale. Anonymous users can exploit it, meaning an attacker needs no account on the target site.
How the flaw works
Drupal core ships with an install.php file used to set up a new site. "Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal," the Drupal Security Team said in its advisory. "This can lead to a site takeover or remote code execution."
The flaw was discovered by Anthropic's OSS Scanner, according to the advisory details.
Permissions matter. The team said some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. The advisory does not spell out every condition needed to trigger the installer path.
What to update, and what to do if you can't
The fixes are in Drupal 10.6.22, 11.3.22 and 11.4.13, covering every currently supported branch. Composer users on the 11.4 line can pull the fix with `composer require 'drupal/core:11.4.13' --update-with-dependencies`.
Admins who cannot upgrade immediately should block access to /core/install.php, either in the web server configuration or in the .htaccess file in the web root. That closes the front door the advisory describes.
Customers of Drupal's paid Steward web application firewall service are already protected from known attack vectors. The team still tells them to upgrade in case other vectors turn up.
A second, lesser bug
The same release fixed a moderately critical gadget chain flaw, CVE-2026-132166 (SA-CORE-2026-018). It is not directly exploitable. An attacker with admin privileges could use it to gain remote code execution, but only if the site also deserializes untrusted data because of a separate flaw.
The exploit clock
The Drupal Security Team's advance notice was blunt. "The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days," it said Monday. "The vulnerabilities are currently rated as critical and at least one can be exploited by anonymous users."
No active exploitation of CVE-2026-132165 has been confirmed as of today, Nov. 19. Given the team's own warning, the lack of confirmed attacks is a narrow window, not a safety margin.
Drupal's installed base is smaller than WordPress's, but it is concentrated in large organizations. The platform is commonly used by government entities, educational organizations, major research universities, and enterprise and media companies that run multi-site installations. Those are the kinds of deployments where a leftover, reachable install.php can persist long after the original setup.
Drupal's recent record
This is not Drupal's first emergency this year. In May, the project confirmed attackers were actively exploiting an SQL injection flaw, CVE-2026-9082, in the database abstraction API. That bug could let them escalate privileges, reach 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, is being abused in attacks.
The U.S. Cybersecurity and Infrastructure Security Agency has flagged five Drupal vulnerabilities as exploited in the wild since November 2021. Two of them have also been used in ransomware attacks.
It is unclear how quickly working exploit code for the installer flaw will appear. The Drupal Security Team has said that could be a matter of hours or days.
Sites that have not updated or blocked /core/install.php are the ones exposed.
Sources used for this briefing
3 links from 3 independent newsrooms (syndicated copies of the same report count once)
These are the sources it draws on, linked so you can verify.