VMTech
Discuss a project →

Drupal releases fixes for critical installer vulnerability

Drupal releases fixes for critical installer vulnerability

Drupal has released security updates for CVE-2026-132165, a critical Drupal core vulnerability that can allow an attacker without credentials to attempt to reinstall a site through the built-in installer. Under specific conditions, the outcome can include site takeover or remote code execution. The Drupal Security Team assigned the issue a score of 18 out of 25 on its risk scale and described the affected configurations as uncommon.

The fixes are Drupal 11.4.13 for the 11.4.x branch, Drupal 11.3.22 for 11.3.x, and Drupal 10.6.22 for 10.6.x. All Drupal releases below 10.6.22 are affected, as are 11.0.0 through releases before 11.3.22 and 11.4.0 through releases before 11.4.13.

Installer remains present after deployment

The issue centres on /core/install.php, the installer included in every Drupal core deployment. It remains on the server after the initial installation. Drupal’s default .htaccess rules do not prevent requests to that file, leaving installer access controls to individual site operators.

Drupal said exploitation is complex and that no attacks were reported in its advisory, but an existing proof-of-concept exploit is recorded. Some attack paths are prevented when the web server cannot write to, or change permissions on, settings.php. That condition makes file permissions and web-server privileges relevant parts of the exposure review.

Update and restrict installer access

Drupal recommends blocking the installer even after applying the patched release. For organisations that cannot update immediately, its updated installer guidance offers three mitigations: deny access in the web-server configuration, add an .htaccess rule, or remove the file and ensure Composer scripts keep it removed.

Drupal Steward customers are protected from known attack vectors, Drupal said, but the project still recommends updating in case additional vectors emerge. The timing also follows the recent Drupal Core SQL injection incident and reinforces the need to treat unauthenticated Drupal core issues as an operational priority rather than a routine maintenance task.

Support status raises the remediation stakes

Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end of life and will not receive a fix. Drupal 11.3.x and Drupal 10 will lose security coverage in December. In the week of November 8, 154,485 of the 528,430 sites reporting usage data to drupal.org—about 29 percent—were on end-of-life branches.

Anthropic’s OSS Scanner found the vulnerability. The automated service, launched on October 8, sends opted-in open-source maintainers findings with a reproducer and, where available, a candidate patch. Drupal’s security team has also said that a rise in reports attributed to AI tools exceeds its current funding capacity, and it will reduce core minor-version security coverage from 12 months to eight months beginning in 2027.

For businesses running Drupal, the immediate action is to inventory versions, deploy the applicable fixed release, block installer access, and verify that settings.php is not unnecessarily writable. Teams on unsupported branches should plan migration work because this flaw has no vendor fix for those releases.

#drupal#cybersecurity#websecurity#vulnerability
Open analytics
On the site 8 views
min read 4 19.11.2026
On Instagram 8 views
On Instagram 3 reach
Instagram

Drupal releases fixes for critical installer vulnerability

Open the post on Instagram ↗