
Editorial illustration; the screens and notice are representative.
Drupal published a critical core advisory on 18 November 2026 for CVE-2026-132165. The issue concerns Drupal’s installer: under specific conditions, an attacker may use it to attempt to reinstall Drupal, potentially taking over a site or achieving remote code execution. The practical question is whether your installed core version is in the affected range, and whether the installer is still reachable or able to change settings.php.
Drupal’s SA-CORE-2026-017 gives the affected versions and fixed releases. Treat that advisory as the remediation authority; CVE databases, EPSS and CISA KEV answer different questions and should not be substituted for the vendor’s version guidance.
Summary
- The advisory affects Drupal versions below 10.6.22, 11.3.22 and 11.4.13 in the branches listed by Drupal; those three releases are the stated fixes.
- Drupal rates SA-CORE-2026-017 as Critical 18/25 on its own scale. That is not a CVSS score.
- Update to the appropriate supported patch release and block access to
/core/install.phpafter installation; verify thatsettings.phpcannot be changed by the web server where your deployment permits. - CVE-2026-132166 is a separate gadget-chain issue that Drupal says is not directly exploitable and requires another unsafe-deserialization flaw.
First, match your installed version to the advisory
Drupal lists the affected ranges as:
- Below 10.6.22 for Drupal 10.
- Drupal 11.0.0 and later, but below 11.3.22.
- Drupal 11.4.0 and later, but below 11.4.13.
The recommended fixes are Drupal 10.6.22, 11.3.22 and 11.4.13 respectively. Drupal states that 10.5.x and below, 11.2.x and below, and Drupal 8 and 9 are end-of-life and do not receive security coverage. If you run one of those branches, do not treat an ordinary patch update as a complete fix; plan a supported upgrade and follow your hosting provider’s guidance.
Check the version in the site’s status report and compare it with the Composer lock file or the exact version deployed to production. The version in a developer’s checkout is not proof of what is running on the public site. If a deployment is in progress, verify the production release after the deployment completes.
What the two Drupal advisories say
SA-CORE-2026-017 describes a remote-code-execution issue in the installer. Drupal says an attacker can, under specific conditions, attempt to reinstall the site. Some exploit paths are mitigated when the web server cannot write to or change permissions on settings.php. The security team also recommends securing the installer after installation.
On the same date, Drupal published SA-CORE-2026-018, CVE-2026-132166. It describes a gadget chain that could be useful if another vulnerability lets an attacker pass unsafe input to PHP’s unserialize(). Drupal explicitly says this issue is not directly exploitable. That distinction matters: it should be included in the same core update, but it is not evidence that every site can be attacked through this chain on its own.
Drupal’s risk rating for the first advisory is 18/25 and for the second 14/25. Those are Drupal’s ratings, not CVSS values. The first advisory’s vector includes E:Proof, but that field is part of Drupal’s assessment; by itself it does not establish that attackers are exploiting this flaw in the wild.
CVE, CVSS, EPSS and KEV answer different questions
A CVE identifier is a shared name for a specific publicly disclosed vulnerability. The format is CVE-YYYY-NNNNN or longer: CVE-2026-132165 identifies this particular Drupal issue. A typical disclosure begins with discovery and a coordinated report to the vendor or a CVE Numbering Authority (CNA). The CNA assigns and publishes the identifier; the vendor works on a fix and coordinates its release; then the advisory and record become public so site owners can respond. The exact path varies, and a CVE number alone does not mean a patch is already available.
The CVE Program, operated by MITRE and its numbering authorities, publishes the record; a CVE Numbering Authority can assign an ID and publish the record as part of disclosure. The NVD, maintained by NIST, may add product applicability, weakness mappings and scoring. Those stages are related, but a vendor advisory remains the source for the product’s fixed versions and upgrade steps. CWE describes classes of coding weakness, while CPE is a structured product name used to identify affected platforms. CVSS communicates technical severity on a 0.0–10.0 scale. In CVSS v3.1, Base metrics describe intrinsic characteristics, Temporal metrics reflect factors that change over time, and Environmental metrics adapt the assessment to a local deployment. CVSS 4.0 uses revised metric groups and scoring, so check which version a record reports before comparing scores.
A high CVSS score is not the same as the risk to your site. Reachability, whether the installer can alter settings, the permissions of the web-server account, compensating controls, exploit evidence and the importance of the site all matter. EPSS is FIRST’s daily estimate of the probability that a vulnerability will be exploited in the wild over the next 30 days; it is a prioritisation signal, not a promise or a measure of local exposure. CISA’s KEV catalog records vulnerabilities with evidence of exploitation. A KEV entry is a strong priority signal, but a vulnerability missing from KEV is not proof it is safe.
At the time this article was prepared, Drupal’s advisory supplied the exact fixed versions and its own risk rating. I could not confirm a separate NVD CVSS score or an EPSS value for these CVEs from the available records, and I could not verify whether either identifier appears in CISA KEV. This article therefore quotes no CVSS or EPSS number and makes no claim of confirmed in-the-wild exploitation. Check the live CVE record, NVD record, EPSS lookup, and CISA KEV catalog if you are triaging today.
A practical response for a site owner
1. Confirm the production version
Record the exact core version and branch for every production site, including multisite deployments. Compare each one with the ranges above. Do not assume that a green scanner result overrides the Drupal advisory: scanners can miss a deployed version, custom document root or outdated node in a cluster.
2. Check the installer control without probing an exploit
After Drupal is installed, the installer should not be available to anonymous visitors. Drupal’s updated installer-hardening guide identifies the path as /core/install.php and recommends blocking access in the web-server configuration where possible. It includes Apache and Nginx examples, plus a check that requests to /core/install.php, /install.php and /core/install.php/foo end with a 403 or 404 response.
Use the Drupal guide with your hosting setup; do not copy a server rule blindly. Managed hosts may already block the route, and Composer-based projects can overwrite hand-edited .htaccess rules during scaffold updates. The guide explains how to preserve an Apache rule in the Composer scaffold configuration. Check that normal site pages and database updates still work after adding a block.
Also review file ownership and permissions for settings.php. The Drupal advisory says preventing the web server from writing to or changing its permissions mitigates some exploit paths. Your deployment process may need write access briefly during installation or configuration changes, so restore the intended permissions afterward rather than applying a broad read-only rule that breaks operations.
3. Update through the project’s normal Composer workflow
Take a recoverable backup of the database and uploaded files, and retain the current code state or deployment release. On a Composer-managed site, update the appropriate supported Drupal core packages in staging first, run database updates and rebuild caches as your normal deployment requires, then deploy the tested lock file to production. Drupal’s core update guide explains the Composer workflow and stresses backing up files and the database.
Do not pin an old vulnerable version simply to avoid a dependency conflict. A lock file should make deployments reproducible, not freeze known-vulnerable code. If the dependency solver cannot reach the fixed release, read the conflict, identify the package holding the constraint, and test an upgrade path in staging. A temporary web-server block on the installer can reduce exposure while you resolve that issue, but Drupal recommends upgrading in the near future; treat the block as a mitigation, not a replacement for the patch. If your hosting provider offers a WAF rule, use it as a temporary control only when the provider confirms it covers this advisory and you can verify the rule is active. Do not invent or copy an unverified rule from a forum.
The advisory says Drupal Steward protects sites from some known attack vectors but does not cover all possible exploits. If you use it, keep the protection in place while you update; do not treat it as a reason to leave core unpatched.
4. Verify the deployment and watch for anomalies
After deploying, confirm the fixed version on production, check the site’s status report, and test login, content pages, forms and any custom installation or multisite workflow. If you manage multiple web nodes, confirm each node has the same code. Review web-server logs around /core/install.php and /install.php for unexpected requests; a request alone does not prove compromise, but unexplained installer activity deserves investigation.
If your site was vulnerable and you find evidence of an attempted reinstall, preserve logs and involve your hosting or incident-response team before restoring or deleting files. Patching closes the known issue; it does not establish whether the site was previously accessed.
How to avoid alert fatigue on the next advisory
Keep a small inventory of Drupal core branches, contributed modules, PHP packages and public sites. Dependency tools such as GitHub Dependabot, Snyk, or Trivy can flag package updates, while composer audit can identify known advisories in Composer dependencies. NVD APIs, operating-system vendor advisories and the platform’s own security feed add separate context; none of these tools automatically knows whether a risky path is enabled or reachable in your production configuration. For this specific issue, that last check means looking at the installer route and server permissions, not simply counting scanner alerts.
For each alert, write down the product and installed version, vendor fixed version, whether the affected feature is present, whether an attacker can reach it, whether the issue is in KEV, and the next owner and deadline. That takes the conversation from “scanner says critical” to an evidence-based decision. Our broader CVE alert triage workflow covers this approach, and our Drupal Composer core-update guide gives more detail on the deployment steps.
My Take
For this advisory, the strongest practical signal is not a database score; it is the vendor’s exact affected range, the installer route and the fixed releases. Match versions first, block the installer after installation, and patch the supported branch. Keep the two Drupal advisories distinct: CVE-2026-132166 is a conditional gadget chain, while CVE-2026-132165 is the installer issue that Drupal rates critical.
Bottom Line
If production is below the fixed version for its supported branch, schedule the Drupal core update promptly and verify it on the live site. Make sure /core/install.php is blocked after installation, preserve settings.php permissions, and use the live CVE, NVD, EPSS and KEV records for any updated scoring or exploitation evidence.
Sources
- Drupal Security Advisory SA-CORE-2026-017
- Drupal Security Advisory SA-CORE-2026-018
- Drupal: Securing the installer (
install.php) - Drupal: Updating Drupal core via Composer
- CVE Program record: CVE-2026-132165
- NVD record: CVE-2026-132165
- FIRST EPSS
- CISA Known Exploited Vulnerabilities catalog
- CVE Program: CNA Operational Rules
- FIRST: CVSS v3.1 specification
- FIRST: EPSS methodology
- MITRE: Common Weakness Enumeration (CWE)
- NVD: Common Platform Enumeration (CPE) FAQ