Drupal Fixes Critical Installer Flaw and Gadget Chain
Drupal core security updates released on 18 November 2026 fix a critical installer vulnerability that could permit site takeover or remote code execution under specific conditions, alongside a separately rated gadget-chain issue that is not directly exploitable. The Drupal Security Team published SA-CORE-2026-017 and SA-CORE-2026-018. Both advisories identify affected Drupal 10 and 11 versions and provide fixes for their supported branches.
The fixed releases are Drupal 11.4.13, Drupal 11.3.22 and Drupal 10.6.22. Administrators running Drupal 11.4.x, 11.3.x or 10.6.x should apply the corresponding security release immediately. The fixes address both advisories. Drupal 11.2.x and earlier, along with Drupal 10.5.x and earlier, no longer receive security coverage. Drupal 10 as a whole is scheduled to reach its end of life on 9 December 2026.
Critical Installer Vulnerability Could Enable Site Takeover
The more severe vulnerability, CVE-2026-132165, carries a Critical rating of 18 out of 25 under Drupal's security risk assessment. It affects the installer, which Drupal ships as core/install.php. Under specific conditions, an attacker can attempt to reinstall an existing site, potentially gaining control of the installation or executing code remotely. The advisory classifies the attack as requiring no authentication but involving complex conditions.
Some exploitation paths are mitigated if the web server cannot write to or change permissions on settings.php. The advisory does not treat those permission settings as protection against every potential attack path. The Security Team recommends both updating Drupal core and restricting access to the installer after installation.
The advisory identifies Anthropic's OSS Scanner as the discoverer of the vulnerability, tracked as ANT-2026-GMRPK0BU. It also confirms that Drupal Steward protects participating sites against known attack vectors for this issue. Drupal Steward does not cover every possible exploit, so protected sites still need the security update.
Second Advisory Addresses a Gadget Chain
The second vulnerability, CVE-2026-132166, is rated Moderately Critical at 14 out of 25. Drupal core contains a sequence of methods, known as a gadget chain, that could be used to achieve remote code execution if another vulnerability allows an application to deserialize untrusted data. The advisory explicitly states that the gadget chain is not directly exploitable. An attacker would first need a separate vulnerability that permits unsafe input to reach PHP's unserialize() function.
The advisory credits Drew Webber, a member of the Drupal Security Team, with reporting the gadget chain. Both vulnerabilities are addressed by the same three supported core releases. The different attack prerequisites mean that the presence of the gadget chain alone does not establish an exploitable remote code execution vulnerability on a site.
Installer Hardening Recommended Alongside Updates
Alongside the security releases, the Drupal Security Team published installer-hardening instructions explaining how administrators can block access to core/install.php after completing installation. The documentation covers Apache and Nginx configurations, restrictions through Apache's .htaccess file and removal of the installer. Server-level restrictions are recommended because they can remain in place when Drupal core is updated.
For Nginx, the official guidance recommends a prefix match such as location ^~ /core/install.php, rather than relying only on an exact-match rule. Some configurations may otherwise process requests containing additional path components, such as /core/install.php/foo. Administrators are advised to test /core/install.php, the redirect from /install.php, and paths with additional components, checking that they return HTTP 403 or 404 responses. These measures supplement the security updates rather than replace them.
The documentation also distinguishes the installer from update.php, which must not be unintentionally blocked by overly broad rules. It warns that manual changes to Composer-managed .htaccess files can be overwritten during scaffolding, including on composer install, unless the additions are maintained through scaffold configuration. Hosting providers may already restrict installer access, so administrators should check existing protections before introducing additional configuration.
The security releases also change the installation process for new Drupal sites. Previously, the installer attempted to correct permissions automatically when settings.php was not writable. The updated installer instead displays an error, requiring the permissions to be corrected before installation can continue. According to the release notes, this change does not affect existing installations.
The Security Team's 16 November advance notice warned that at least one of the vulnerabilities could be exploited without authentication and that multiple site configurations were affected. The 18 November advisories now provide the technical distinctions, fixed versions and additional protective guidance needed for administrators to act. Neither advisory states that exploitation of production sites has been confirmed; this should not be read as evidence that exploitation has not occurred.
References
-
Drupal 11.4.13 | Drupal.org (18 November 2026)
-
Drupal 11.3.22 | Drupal.org (18 November 2026)
-
Drupal 10.6.22 | Drupal.org (18 November 2026)
-
Securing the installer (install.php) | Drupal.org (18 November 2026)
