Incident sheet · /security
- System
- Security & Risk
- Filed
- Read
- 3 min · 560 words
- Severity
- Routine
Drupal Patches Critical RCE Flaw Exploitable by Anonymous Users
Drupal patched CVE-2026-132165, a critical RCE flaw letting anonymous attackers reinstall the CMS and take over sites. Fixes: 10.6.22, 11.3.22, 11.4.13.

Event log
- CVE-2026-132165 is a critical RCE flaw in Drupal core exploitable by anonymous users; found by Anthropic's OSS Scanner.
- Fixed versions: Drupal 10.6.22, 11.3.22, and 11.4.13, released Wednesday.
- Drupal Steward WAF customers already protected against known vectors but should still upgrade.
- CISA has flagged 5 Drupal vulnerabilities exploited in the wild since November 2021; two used in ransomware attacks.
- Workaround: block access to /core/install.php via web server config or .htaccess.
Drupal has shipped emergency patches for a critical remote code execution flaw that anonymous attackers can exploit to reinstall the CMS and take over vulnerable sites — and the security team warns working exploits could appear within days.
The vulnerability, tracked as CVE-2026-132165, affects Drupal core, the content management system behind large multi-site deployments at government agencies, universities, research institutions and major enterprise and media organizations. Anthropic's OSS Scanner discovered the flaw.
How does the attack work?
The mechanism is unusually direct. Drupal core ships with an install.php file used to set up new installations.
"Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. This can lead to a site takeover or remote code execution," the Drupal Security Team warned in a Wednesday advisory. "Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php."
In plain terms: if an unauthenticated attacker can reach the installer under the right server conditions, they can effectively rebuild the site under their control. No credentials are required on at least one known exploit path.
What should administrators do now?
The fix comes in three versions, depending on the branch an organization runs:
- Drupal 10.6.22
- Drupal 11.3.22
- Drupal 11.4.13
Customers of the paid Drupal Steward Web Application Firewall service are already protected against the known attack vectors. The security team still urges them to upgrade, in case researchers or attackers find additional paths into the installer.
Teams that cannot patch immediately should block access to /core/install.php at the web server configuration level or via the .htaccess file in the web root. That single change closes the door the installer represents.
The team signaled the urgency in advance. "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 in a Monday warning that also noted at least one of the flaws can be exploited by anonymous users.
What else was patched on Wednesday?
The same release fixes a moderately critical gadget chain vulnerability, CVE-2026-132166. Attackers with admin privileges can chain it to achieve remote code execution, but only if the application deserializes untrusted data due to a separate security flaw. It is a secondary risk that becomes real only in combination with another bug — still worth patching in the same maintenance window.
Is Drupal under active attack elsewhere?
Yes, and the record explains the team's urgency. In May, Drupal confirmed attackers were actively exploiting an SQL injection flaw, CVE-2026-9082, in the database abstraction API. That bug allowed privilege escalation, access to sensitive data, or remote code execution on unpatched servers.
More recently, Drupal warned that a critical access bypass vulnerability in the Commerce Core module, CVE-2026-118539, is being abused in live attacks.
The pattern is broad enough that the US Cybersecurity and Infrastructure Security Agency has flagged five Drupal vulnerabilities as exploited in the wild since November 2021. Two of those five have also been used in ransomware attacks.
For enterprises running Drupal across dozens or hundreds of sites, the practical math is stark: one patch cycle now versus the risk of an anonymous takeover later.
Patch first; harden the installer second; assume exploit code arrives within days.
via bleepingcomputer.com (Source)
More from Amara Osei
Show full bio
Correspondent covering regulation, policy and their impact on enterprise information technology and the leaders who run at CIO Monitor.
187 articles
The newsroom digest
One email a day with the stories that matter. No noise.
Cross-references
- Microsoft's October Patch Tuesday Ships 1,408 CVEs, One Actively Exploited
- PHP flaws make security patching a customer-experience priority
- PHP2Shell Campaign Wiped VMware ESXi Hosts via Check Point Gateways
- NoisyTCP: 11-Year-Old Kernel Flaw Crashes Nginx, Apache and SSH Servers
- Fake GitHub Security Tools Compromise 2,000 Windows Systems