Drupal core installer flaw CVE-2026-132165 reported exploited: update to 10.6.22, 11.3.22 or 11.4.13 or later
Identifiers: CVE-2026-132165 · CVE-2026-132166 · SA-CORE-2026-017 · SA-CORE-2026-018
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
On 18 November 2026 the Drupal Security Team published two core advisories. SA-CORE-2026-017 (CVE-2026-132165) concerns conditions under which the installer path of an already installed site can be reached. On 20 November 2026 the team updated that advisory, raising it from Critical, 18/25, to Highly critical, 20/25, with an exploitation rating of E:Exploit, and stating it had received a report that the flaw was exploited on live sites as early as 19 November 2026 at 19:00 UTC. SA-CORE-2026-018 (CVE-2026-132166) is unchanged: it is rated 14/25, is not Critical, and concerns a conditional deserialization chain that only becomes exploitable when combined with a separate unsafe deserialization flaw. Both are fixed in Drupal 10.6.22, 11.3.22 and 11.4.13.
Impact
For SA-CORE-2026-017, where the reachability conditions hold, an attacker without credentials could reach installer functionality on a running site, with possible outcomes up to site takeover or remote code execution. The Drupal Security Team now rates it E:Exploit and says it received a report of exploitation on live sites; the advisory does not give counts, name affected sites or businesses, or say whether the reported activity was the first. SA-CORE-2026-018 remains rated theoretical: on its own it has no demonstrated path, it becomes relevant only if a separate unsafe deserialization flaw exists on the site, and the exploitation report does not apply to it. Preventing the web server account from writing to or changing permissions on settings.php mitigates some SA-CORE-2026-017 paths only, so it reduces exposure but does not replace the update. Applying the fix stops the flaw going forward but cannot show whether a site was already accessed before patching.
Who is affected
Affected: Drupal core <10.6.22, >=11.0.0 <11.3.22, and >=11.4.0 <11.4.13. Fixed: 10.6.22, 11.3.22 and 11.4.13. These are version floors: any later supported release in the same branch also contains the fix, and a site already on a later patched release should not be moved back to the exact floor. Drupal 10.5.x and older within the 10 series, 11.2.x and older within the 11 series, and Drupal 8 and 9 no longer receive security coverage and get no fix; those sites must move to a supported line. Drupal Steward protection for the known vectors of SA-CORE-2026-017 applies only to its subscribers and, according to the vendor, does not remove the need to update. The 20 November release notes for the three fixed versions describe a separate theme registry regression that affects some custom and contributed code, including Search API. The notes say Drupal 11.4.14 is planned to address that regression; it is not the security fix, and its availability is not verified here. The release notes suggest affected 11.3.22 and 10.6.22 sites consider moving to the 11.4 line to receive that regression fix once it is available. Distribution and hosting panel packages need their own confirmation.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| Drupal core installer (CVE-2026-132165) | <10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13 | 10.6.22, 11.3.22 and 11.4.13 on the respective supported branches |
| Drupal core deserialization chain (CVE-2026-132166) | <10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13 | 10.6.22, 11.3.22 and 11.4.13 on the respective supported branches |
Exploitation evidence
Exploitation reported. The Drupal Security Team's 20 November 2026 update to SA-CORE-2026-017 states it received a report that CVE-2026-132165 was exploited on live sites as early as 19 November 2026 at 19:00 UTC, and the advisory's exploitation rating was raised to E:Exploit. The advisory does not give counts, identify affected sites or businesses, or say whether this was the first attack. SA-CORE-2026-018 is still rated theoretical and no exploitation has been reported for it. Site owners cannot tell from the advisory whether their own site was affected; the only way to know is to review logs and changes for the period the site was exposed.
Actions
- List every Drupal site you operate, including staging, development and client copies, and record its exact core version and branch.
- Take a protected backup for recoverability, then update each site promptly to at least the fixed version for its branch, 10.6.22, 11.3.22 or 11.4.13, or a later supported release. Sites already on a later patched release need no change for this flaw. Do not hold the security update for 11.4.14 or any later release.
- Plan the rollout around the known theme registry regression in the fixed releases. If a staging copy exists and testing fits an urgent safe rollout, check normal page templates and Search API behaviour there first; otherwise patch live and validate those same areas immediately after. Drupal 11.4.14 is planned in the release notes to address the regression, but its availability is not verified here.
- For sites on 10.5.x or older, 11.2.x or older, or Drupal 8 or 9, plan a move to a supported line now; no fix will be issued for those branches.
- Secure the installer following the official Drupal guide, both while an update is pending and after it is applied, since the advisories recommend this for patched sites too. Where an update must wait, also ask your host or developer to make settings.php not writable or changeable by the web server account. Treat both as partial measures for SA-CORE-2026-017 only, not as a fix.
- If a site was exposed while unpatched, ask your provider or agency to confirm the deployed version on the live server and to review web server logs, file changes, user accounts and configuration for unexpected installer access or other unexplained changes. Scope the review to the period your site was exposed, including the window from 19 November 2026 at 19:00 UTC that the Drupal Security Team says was reported to it, rather than only the period after the advisory was published.
- If anything suspicious is found, preserve logs and copies of the affected files before cleaning up and seek incident response help; a successful patch does not confirm that no earlier compromise occurred.
Unknowns
- Whether a given site meets the reachability conditions for SA-CORE-2026-017 depends on its configuration and hosting, and is not known without checking.
- The Drupal Security Team has not stated the scale of the reported exploitation of SA-CORE-2026-017, which sites were targeted, or whether the 19 November activity was the first. Whether a specific site was accessed before it was patched cannot be determined from the update itself and requires a review of its own logs and changes.
- Whether a separate unsafe deserialization flaw exists on a given site, which SA-CORE-2026-018 needs, depends on contributed and custom code.
- Whether a particular site is affected by the theme registry regression in the fixed releases depends on its custom and contributed code, and the actual release of Drupal 11.4.14 is not verified here.
- Backport status for distribution packages and hosting panels is not confirmed here.
Sources
- Drupal Security Team https://www.drupal.org/sa-core-2026-017
- Drupal Security Team https://www.drupal.org/sa-core-2026-018
- Drupal project https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-the-installer-installphp
- Drupal project https://www.drupal.org/project/drupal/releases/10.6.22
- Drupal project https://www.drupal.org/project/drupal/releases/11.3.22
- Drupal project https://www.drupal.org/project/drupal/releases/11.4.13
Change history
- — Published: 20 November 2026: record created for Drupal advisories SA-CORE-2026-017, a Critical 18/25 installer flaw with a rated proof of concept, and SA-CORE-2026-018, a 14/25 conditional deserialization issue, both fixed in 10.6.22, 11.3.22 and 11.4.13, with no established in-the-wild exploitation.
- — Correction: 21 November 2026 correction: the Drupal Security Team updated SA-CORE-2026-017 on 20 November 2026, raising it from Critical 18/25 (E:Proof) to Highly critical 20/25 (E:Exploit) and stating it had received a report that CVE-2026-132165 was exploited on live sites as early as 19 November 2026 at 19:00 UTC. Earlier statements in this briefing that no exploitation in the wild was known and that the flaw was rated at proof-of-concept level are superseded. SA-CORE-2026-018 (CVE-2026-132166) is unchanged at 14/25, theoretical on its own. The 20 November release notes for 10.6.22, 11.3.22 and 11.4.13 describe a separate theme registry regression affecting some custom and contributed code, including Search API, with 11.4.14 planned for that regression and its availability not verified here; owners should still apply the security fix now and not wait. Guidance on post-patch testing, log review scoped to each site's exposure window, and evidence preservation was added.