A Drupal security update released on November 18 fixes a critical flaw that could let someone without an account take control of a vulnerable website. The Drupal Security Team warned that attackers could develop an exploit within hours or days of the release.

An installer flaw puts existing sites at risk

The vulnerability, tracked as CVE-2026-132165, affects the installer that ships with Drupal core. Under certain conditions, a visitor can use it to start a new installation on a site that already runs Drupal. That could give the visitor control of the site or allow them to run code remotely. Anthropic’s OSS Scanner discovered the flaw.

Server permissions affect the risk. According to the security team, some routes to exploitation depend on whether the web server can write to Drupal’s settings.php configuration file or change its permissions. Restricting both capabilities limits those routes, but administrators still need to apply the fix.

Which Drupal releases include the fix?

The Drupal security update is available in versions 10.6.22, 11.3.22 and 11.4.13. Administrators can install the release that matches their current branch. If they need more time to upgrade, the team recommends temporarily blocking web access to /core/install.php. They can apply that restriction in the web server configuration or in the .htaccess file at the root of the website.

For sites using Drupal Steward, the paid web application firewall already blocks the attack methods the team knows about. Even so, the team advises those customers to upgrade because researchers or attackers could discover another way to reach the vulnerable installer.

A second flaw requires administrator access

The same release addresses CVE-2026-132166, which Drupal rates as moderately critical. Exploiting this second flaw requires administrator privileges and a separate weakness that causes the application to reconstruct data objects from untrusted input. With both conditions in place, an attacker could run code on the site.

Drupal’s warning about a possible exploit for the installer flaw follows confirmed attacks against earlier vulnerabilities. In May, Drupal reported that attackers were exploiting an SQL injection flaw in its database layer. More recently, attackers exploited an access-control flaw in the Commerce Core module. For the newly patched installer issue, the team’s warning concerned how quickly attackers might develop an exploit.


0 responses to “Drupal security update fixes flaw that could expose sites”