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 Urges Core Updates as Installer Flaw Carries Proof-Level Exploit Rating, No Attacks Confirmed

Since Drupal shipped fixes Wednesday, Nov. 18 for the critical installer flaw CVE-2026-132165, the full advisory text has filled in the picture. It shows how the flaw was scored, who found it, and what sits next to it.
The Drupal Security Team published two advisories, not one. SA-CORE-2026-017 covers the installer flaw. SA-CORE-2026-018 covers CVE-2026-132166, a gadget-chain bug in core.
How Drupal scored the installer flaw
Drupal rates CVE-2026-132165 as Critical, 18 out of 25. The risk vector reads AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon. In plain terms: the attack is complex, needs no authentication, and can compromise confidentiality and integrity completely. The exploit tag is "Proof," and the number of sites exposed is rated "Uncommon."
The advisory says that under specific conditions an attacker can use core/install.php to try to reinstall Drupal, which "can lead to a site takeover or remote code execution." Some exploit paths are blocked if the web server cannot write to or change permissions on settings.php. The advisory does not claim that setting covers every path.
The threat-intelligence tracker Mallory reports that a proof of concept for the flaw exists. The Dutch National Cyber Security Centre (NCSC), in its own notice, said no public exploit code was available at the time. Nobody has reported active attacks on either of this week's flaws.
The Drupal Security Team warned in a Monday advance notice that "exploits might be developed within hours or days." It said at least one of the vulnerabilities can be exploited by anonymous users.
The second bug
CVE-2026-132166 is rated Moderately Critical, 14 out of 25. Drupal core contains a chain of methods that could yield remote code execution, but only if a separate vulnerability lets an application deserialize untrusted data. Exploiting it requires administrator privileges. It is not directly exploitable on its own.
Who found it
The installer flaw was discovered by Anthropic's OSS Scanner and logged as ANT-2026-GMRPK0BU. The advisory credits Lee Rowlands of the Drupal Security Team, Pamela Barone, Scott Euser, Stephan Zeidler and Tyler Nighswander as reporters. A long list of Drupal Security Team members, including Alex Pott, Benji Fisher, David Strauss and Jess (xjm), is credited with the fix.
Anthropic describes the scanner as an opt-in tool whose automated output can contain false positives and does not replace manual validation. Here the Drupal team confirmed the finding and shipped patches.
Who needs to move
The fixed releases are Drupal 10.6.22, 11.3.22 and 11.4.13. Drupal 11.2.x and earlier, and 10.5.x and earlier, no longer receive security coverage. Drupal 8 and 9 are also end-of-life.
The Drupal 10 line as a whole is scheduled to reach end of life on Dec. 9, 2026. That is three weeks away, so anyone patching 10.6.x today will soon face a second migration.
Sites on the paid Drupal Steward web application firewall are already protected from known attack vectors, the advisory says. It adds that they should still upgrade in case other vectors are found.
Admins who cannot update immediately are told to block access to /core/install.php in the web server configuration or the .htaccess file in the web root. The Security Team also recommends securing or removing the installer after installation. The Dutch NCSC gives the same advice.
A busy year for Drupal
The patches land after a run of Drupal problems. In May, Drupal confirmed attackers were exploiting SQL injection flaw CVE-2026-9082 in the database abstraction API. More recently, Drupal warned that a critical access bypass in the Commerce Core module, CVE-2026-118539, is being abused. Mallory's timeline also lists a critical remote code execution fix in Field UI on Oct. 14, with at least one path requiring no login.
The U.S. Cybersecurity and Infrastructure Security Agency has flagged five Drupal vulnerabilities as exploited in the wild since November 2021. Two were used in ransomware attacks.
It is not yet clear how quickly working exploit code appears now that patches are public. Drupal's own timeline says hours or days.
The advisory's exploit tag and the NCSC's statement point in different directions, and no vendor or agency has yet confirmed either an attack or a public exploit.
Sources used for this briefing
7 links from 7 independent newsrooms (syndicated copies of the same report count once)
These are the sources it draws on, linked so you can verify.