Summary
- Drupal advisory SA-CORE-2026-017 addresses CVE-2026-132165, a critical vulnerability involving its installation process.
- Corrected releases are Drupal 10.6.22, 11.3.22 and 11.4.13, while older unsupported branches require attention.
- Restrictions on installer access and permissions protecting settings.php can reduce exposure, but Drupal recommends upgrading even where mitigations are present.
Drupal has released security updates for a critical vulnerability that could allow attackers to take over affected websites or execute code remotely by abusing the content management system's installation process.
The Drupal Security Team disclosed CVE-2026-132165 on 18 November 2026 through advisory SA-CORE-2026-017. The weakness involves the install.php functionality used to configure Drupal installations.
Under specific conditions, an attacker may be able to use that functionality to attempt to reinstall an existing site, potentially obtaining control over the application.
Drupal classifies the vulnerability as critical, with a security risk rating of 18 out of 25 under its advisory system. The disclosure does not confirm active exploitation, and the severity assessment should not be presented as evidence that websites have already been compromised.
Installation functionality can expose existing websites
Drupal is used to operate websites, content platforms and applications for businesses, public institutions and other organisations.
During initial deployment, its installer configures important application settings and establishes the environment required for the site to function.
Those capabilities are necessary when a site is first installed but should not remain accessible to unauthorised users in a manner that permits changes to an existing installation.
The disclosed vulnerability concerns conditions under which the installation process may be invoked again against a site that is already operational.
If an attacker can successfully abuse that process, the consequences may include taking control of the site or executing code with the permissions available to the affected application.
The Drupal advisory does not describe every installation as automatically exploitable. Exposure depends on the affected software version and the conditions governing access to the installer and its supporting configuration files.
That distinction is important when assessing the scale of potential risk. A critical vulnerability may warrant urgent remediation even where its exploitation requires particular configuration conditions.
The existence of the weakness does not establish that an individual website has suffered unauthorised access.
Three supported branches receive fixes
The security team has published corrected versions for the supported Drupal branches identified in the advisory.
Organisations using Drupal 10.6 should update to version 10.6.22, while those using Drupal 11.3 and 11.4 should update to versions 11.3.22 and 11.4.13 respectively.
The advisory identifies affected versions as those before Drupal 10.6.22 and the specified ranges within Drupal 11.
Drupal also notes that version 10.5 and earlier, together with Drupal 11.2 and earlier, have reached end of life and no longer receive normal security coverage.
Drupal 8 and Drupal 9 are also unsupported.
These distinctions affect organisations maintaining older websites that remain operational despite running software branches no longer supported by the project.
A site may continue serving content after its software reaches end of life, but administrators cannot assume that a corrected release will be provided for its existing branch.
Upgrading may therefore require additional compatibility work involving modules, themes and application customisations.
That work can be particularly demanding where a website supports business processes extending beyond publishing content, including customer interactions or connections to internal systems.
File permissions provide partial mitigation
The Drupal Security Team identifies protection of settings.php as an important factor in reducing certain exploitation paths.
The file contains configuration information required by the application. Some methods of exploiting the installer weakness are mitigated when the web server cannot write to the file or change its permissions.
Drupal also recommends restricting access to its installer after the initial installation is complete.
The project's security guidance explains that the installation entry point remains part of the deployed application and should not be left available for unauthorised use.
Those protections can reduce the opportunities for exploitation, but the advisory does not state that they eliminate every possible attack path.
Drupal consequently recommends installing corrected releases even where file permissions or other controls appear to protect an affected site.
The distinction between mitigating a known path and removing the underlying vulnerability is relevant to organisations managing large numbers of websites.
Configuration safeguards may provide additional protection while maintenance is arranged, but the appropriate corrective version still needs to be deployed and verified.
Drupal Steward protection has defined limits
Drupal says installations using Drupal Steward are protected against currently known attack vectors associated with the vulnerability.
However, the project still recommends upgrading those installations because additional methods of exploiting the underlying weakness could be identified.
A protective service may block activity associated with a known vulnerability without changing the vulnerable application code itself.
Such arrangements can therefore support defence while leaving responsibility for software maintenance with the organisation operating the site.
Administrators need to establish whether the protection applies to their particular installation and whether other exposed components require separate updates.
Automated research contributed to the discovery
The advisory credits Anthropic's OSS Scanner with identifying the vulnerability under the reference ANT-2026-GMRPK0BU.
Automated code analysis can help identify security weaknesses in widely used open-source software, but findings still require technical assessment and coordinated remediation.
In this case, the Drupal Security Team published the affected-version assessment, mitigation information and corrected releases through its normal advisory process.
The vulnerability is separate from previously reported security issues involving Drupal Commerce. It affects Drupal core's installation functionality rather than the Commerce module's application behaviour.
For organisations operating Drupal sites, determining exposure requires checking the deployed version, the availability of the installer and the permissions governing application configuration.
Where unauthorised activity is suspected, remediation and incident investigation remain separate tasks. Updating the affected software removes the identified vulnerability but does not establish whether a system was previously compromised.
Drupal has not reported confirmed exploitation of CVE-2026-132165 in the advisory. The corrected releases and installer security guidance are available, with the security team continuing to recommend upgrades for affected deployments.




