Drupal: close the installer and validate the site update
A Drupal update needs to reach every site while preserving its operation. Treat installer access, the delivered version and acceptance testing as parts of the same change.
Lire en portugaisBy Pentesty
Define the vulnerability before planning the change
The Drupal advisory dated November 18, 2026 describes CVE-2026-132165: under specific conditions, the installer can enable site takeover or code execution. Its rating is critical, 18/25. Corrective versions are 10.6.22, 11.3.22 and 11.4.13; earlier unsupported branches require migration. The document does not report confirmed exploitation.
Start with one site and identify its owner, domain, hosting arrangement, core version and dependencies. Include forgotten installations, accessible staging environments and additional sites on the same server. Give each deployment a verifiable decision, deadline and acceptance owner. A general server inventory does not establish that responsibility.
Prepare the update as a service change
Agree on a maintenance window, backup and recovery procedure before changing the environment. Identify who can stop deployment and which signals justify that decision. Record the approved package and expected configuration. For externally managed platforms, request evidence connecting the change to your site, alongside the provider’s general confirmation.
Choose representative functions: publishing, authentication, forms and integrations the business actually uses. Let business needs determine the list. Our analysis of the running PHP service helps trace an update to the service receiving requests, including deployments with multiple replicas or images.
Verify that restrictions survive deployment
The installer documentation recommends blocking access after installation and distinguishes install.php from update.php. Manual changes to Composer-managed files can disappear. The guide calls for testing installer paths, including variants with text after the filename, expecting a blocked response while keeping legitimate updates available.
Place the restriction where your team can maintain and review it. Preserve the configuration, authorized external test result and environment identity. Repeat verification after the build and deployment. A screenshot from before the update does not show that the new delivery preserved the control across every domain and virtual host.
Include compatibility in release acceptance
Version 11.4.13 is available. Its notes identify a theme-registry regression affecting some modules and custom code, including Search API, with a fix planned for 11.4.14. That calls for compatibility testing and project follow-up; a planned release is not an already delivered package.
Compare before-and-after results using a sample representing the site’s features. Record observed errors and the decision about continued operation. When a function fails, connect the open issue to its technical owner and affected business process. Distinguish security remediation from functional quality so that neither conclusion hides the other.
Close with coverage and named outstanding work
The final record should connect the observed version, applied delivery, installer restriction and functional tests. Identify sites examined directly and those depending on external confirmation. Our exposure-window analysis complements this work by connecting discovery, decisions and deployment on a timeline.
Bring the update into the normal delivery process too. Assign responsibility for reviewing new images, rebuilds and Composer changes. If suspicious modifications appear, open a separate investigation and preserve available records. A completed upgrade alone cannot explain earlier activity or automatically restore confidence in content and access.
To make the record useful at the next maintenance window, note who performed each check, when it was observed and which deployment it concerns. Choose evidence another person can interpret without repeating the entire investigation. If coverage depends on a sample, explain its selection and what remains outside it. That record helps compare later changes, request specific answers from hosting providers and recognize when a new production site has bypassed the same acceptance criteria.
Frequently asked questions
Does blocking the installer replace the update?
The official advisory describes mitigation of some paths through settings.php permissions but still recommends updating. Record temporary protection and follow the corrective delivery to completion.
What evidence should hosting providers supply?
Request the site identity, deployed version, change time and agreed test results. A statement about the entire platform needs a clear connection to the installation your business uses.
How should a post-update failure be handled?
Preserve the error and assess its impact with the owners. Use the approved recovery plan, keep the installer restricted and record anything still requiring a correction or test.
When can the work be closed?
Close the agreed scope when delivery and functional evidence are available and exceptions have owners. Updating, restricting access and investigating possible compromise each require their own traceable conclusions.
Sources and references
- Cyber Insider: November 20 report on the Drupal installer
- Drupal: SA-CORE-2026-017, published November 18
- Drupal: documentation on securing the installer
- Drupal: version 11.4.13 availability and release notes
Original Pentesty analysis, published November 20, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.