Skip to main content
CybersecurityVulnerability Management

Drupal Fixes Installer Flaw That Exposes Sites to Unauthenticated Attacks

Server room with rack of servers, network switches, and cables.

CVE-2026-132165 can allow an unauthenticated attacker to use Drupal’s built-in installer to attempt to reinstall a site, the Drupal Security Team disclosed, warning that under specific conditions the flaw can lead to site takeover or remote code execution.

How CVE-2026-132165 operates

The vulnerability resides in Drupal core’s installer, the file shipped in every copy of core as /core/install.php. That file remains on sites after installation by default, and core’s default .htaccess rules do not block requests to it—so blocking access is left to each site. The security team rated the flaw critical, 18 out of 25 on the project’s risk scale.

The advisory says exploitation is complex but records a proof-of-concept exploit. Where a vulnerable configuration allows the installer to run, an unauthenticated attacker can attempt to reinstall the site; in some exploit paths that can produce a site takeover or remote code execution. The advisory notes that certain exploit paths are blocked when the web server cannot write to or change permissions on settings.php.

Fixed releases and immediate operational steps

Fixed releases for all supported branches were shipped yesterday. The project’s release notes list the exact updates:

  • Drupal 11.4.x: update to 11.4.13
  • Drupal 11.3.x: update to 11.3.22
  • Drupal 10.6.x: update to 10.6.22

The Drupal Security Team recommends that sites block the installer even after updating. For sites that cannot update immediately, the project’s installer guidance (updated yesterday) outlines three temporary options: add a deny rule in the web server configuration, add an .htaccess rule to block the installer, or remove the installer file and keep it removed via Composer scripts. The advisory reports no attacks to date, but the team had warned site owners earlier in the week to set aside time for the update because exploits “may be developed within hours or days.”

Sites using the Drupal Steward protection service are already protected from known attack vectors, the team said, but they should still update in case new vectors emerge.

Affected releases, end-of-life branches, and reported exposure

The project said every release below 10.6.22 is affected, along with Drupal 11 releases from 11.0.0 before 11.3.22 and from 11.4.0 before 11.4.13. Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end-of-life and receive no fix.

The advisory also notes where coverage is shifting: the 11.3.x branch and Drupal 10 will lose security coverage altogether in December under the project’s support schedule. In the week of November 8, 154,485 of the 528,430 sites reporting usage data to drupal.org—about 29 percent—were running end-of-life branches.

Anthropic’s OSS Scanner, the security workload, and recent patch history

The flaw was found by Anthropic’s OSS Scanner, an automated service the AI company launched on October 8 to scan opt-in open-source projects for vulnerabilities. According to Anthropic’s launch announcement, findings go to maintainers without human review and include a reproducer and, where available, a candidate patch.

Drupal’s security team said on November 2 that a surge of security reports, which it attributes to AI tools, is “more than it can sustain at its current funding,” and that it will cut security coverage for core minor versions from 12 months to 8 starting in 2027. This is the second critical remote code execution flaw fixed in Drupal core in two months—following the Field UI flaw patched on October 14, which also included at least one exploit path that needed no login.

What this means for technologists, procurement leaders, and open-source maintainers

  • Technologists and security teams: apply the listed updates (11.4.13, 11.3.22, or 10.6.22) immediately where applicable; block the installer in webserver or .htaccess if you cannot update; verify whether settings.php is write-protected to understand exploitability.
  • Affected enterprises and procurement leaders: inventory deployments—note that roughly 29 percent of reporting sites were on end-of-life branches in the relevant week—and prioritize remediation or migration for systems no longer receiving fixes.
  • Open-source maintainers and funders: expect continued volume from automated scanners and a compressed support window beginning in 2027; the project has already signaled resource strain by reducing minor-version coverage from 12 months to 8.

For operators, the immediate calculus is simple and concrete: update to the fixed versions and block the installer if you cannot. For the project as a whole, the reminder is equally stark—automated tools can find problems fast, and maintainers say their funding and support windows will be shorter as a result. Whether those two trends will converge into more urgent risk for the many sites running end-of-life code is the practical question the community now faces.

https://thehackernews.com/2026/11/drupal-patches-critical-installer-flaw.html