Security notice
Run a site on Drupal? A flaw in the installer can lead to a site takeover or remote code execution. Update to 11.4.13, 11.3.22 or 10.6.22 today.
On November 18, 2026, the Drupal Security Team published advisory SA-CORE-2026-017 for Drupal core, tracked as CVE-2026-132165. Drupal rates it Critical, 18 out of 25, on its own scale (not CVSS). Drupal core ships with an install.php file used to install the software. The advisory says that under specific conditions, an attacker can use the installer to attempt to reinstall Drupal, and that this can lead to a site takeover or remote code execution. The fixed releases are Drupal 11.4.13, 11.3.22 and 10.6.22. Drupal 11.2.x and below, 10.5.x and below, and Drupal 8 and 9 are end-of-life and do not receive a patch; Drupal tells those sites to follow its guide on securing the installer. The same releases also fix SA-CORE-2026-018 (CVE-2026-132166), a moderately critical gadget chain that Drupal says is not directly exploitable. Drupal's advisory does not report in-the-wild exploitation. As of November 18, 2026, we found no report of attacks on live sites, and CISA's Known Exploited Vulnerabilities Catalog does not list either CVE. If you run Drupal, update to the fixed release for your branch today. EverThread does not test for this. (Drupal SA-CORE-2026-017, Nov 18; SA-CORE-2026-018, Nov 18)
What happened
- The installer flaw. CVE-2026-132165 is described in Drupal advisory SA-CORE-2026-017, published November 18, 2026. Drupal says core ships with an
install.phpfile for installing Drupal core. "Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. This can lead to a site takeover or remote code execution." Drupal also says some of those paths are mitigated if the web server cannot write to or change permissions onsettings.php, and that in addition to upgrading, the Security Team recommends securing the installer after installation. (Drupal SA-CORE-2026-017) - Severity. Drupal rates CVE-2026-132165 as Critical, 18 out of 25, on its own scale (not CVSS). The advisory's risk line is AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon. (Drupal SA-CORE-2026-017)
- The same-day gadget-chain advisory. The same releases also fix CVE-2026-132166, described in SA-CORE-2026-018 and rated moderately critical, 14 out of 25, on Drupal's scale. Drupal says core contains a chain of methods that could be used if an insecure deserialization vulnerability already exists on the site, and that this "gadget chain" presents no direct threat on its own. The advisory states: "This issue is not directly exploitable." It is mitigated, Drupal says, because a separate vulnerability must be present that lets an attacker pass unsafe input to
unserialize(). (Drupal SA-CORE-2026-018) - The fix. For Drupal 11.4.x, update to 11.4.13. For 11.3.x, update to 11.3.22. For 10.6.x, update to 10.6.22. Those release pages were live on Drupal.org when we checked on November 18, 2026. (SA-CORE-2026-017, 11.4.13, 11.3.22, 10.6.22)
- End-of-life versions get no patch. Drupal says 11.2.x and below, 10.5.x and below, and Drupal 8 and 9 are end-of-life and do not receive security coverage. If you cannot upgrade immediately, or you are on an end-of-life version that will not get a patch, Drupal says to follow its instructions for securing the installer. (SA-CORE-2026-017, Drupal's guide on securing install.php)
- Pre-release builds. On November 16, 2026, Drupal public service announcement PSA-2026-11-16 also listed Drupal 12.0.0-beta3 and 11.5.0-beta1 as affected, and said new beta or release candidate versions would follow the updates for the supported branches. As of November 18, 2026, we could not find a newer 12.0.0 or 11.5.0 beta or release candidate on Drupal.org. If you run one of those pre-release builds, watch Drupal's security advisories for a fixed build and follow the installer-securing steps in the meantime. (PSA-2026-11-16)
- Drupal Steward. The SA-CORE-2026-017 advisory says this issue is being protected by Drupal Steward. Sites that use Drupal Steward are already protected from some known attack vectors, but Drupal says that protection will not cover all possible cases, and that sites should still upgrade. (SA-CORE-2026-017)
- No in-the-wild exploitation reported. Drupal's advisory does not report attacks on live sites. As of November 18, 2026, we found no report of in-the-wild exploitation of CVE-2026-132165 or CVE-2026-132166. CISA's Known Exploited Vulnerabilities Catalog (catalog version 2026.11.18, 1,786 entries when we checked on November 18, 2026) does not list either CVE. (SA-CORE-2026-017, CISA KEV)
Who should worry
Any website running Drupal core on a version before the fixed releases above, including end-of-life branches that will not get a patch, and the 12.0.0-beta3 and 11.5.0-beta1 pre-release builds named in PSA-2026-11-16. If you do not run Drupal, this notice does not apply to you.
What to do now
- Update to the fixed release for your branch today. Back up the site first. If you use Drupal 11.4.x, update to 11.4.13. If you use 11.3.x, update to 11.3.22. If you use 10.6.x, update to 10.6.22. Confirm the installed version after the update. These updates also include the SA-CORE-2026-018 fix. (SA-CORE-2026-017, SA-CORE-2026-018)
- Secure the installer after installation. In addition to upgrading, the Drupal Security Team recommends securing the Drupal installer. Follow Drupal's guide on securing install.php. (SA-CORE-2026-017)
- If you cannot update immediately, or you are on an end-of-life version, follow that same guide now. Drupal 11.2.x and below, 10.5.x and below, and Drupal 8 and 9 do not receive a patch for these flaws. Plan to move to a supported release. (SA-CORE-2026-017, securing the installer)
- If you use Drupal Steward, Drupal says you are already protected from some known attack vectors for SA-CORE-2026-017, but not from all of them. Still update. (SA-CORE-2026-017)
- Check for signs of tampering. Updating closes the flaw; it does not undo a takeover that may already have happened. Look for unexpected administrator accounts, unexpected changes to
settings.phpor other site settings, and other signs you do not recognize. If you find signs of a break-in, change passwords, tell affected users, and ask your developer or host to investigate.
What to send your developer, agency or host
Please check whether our site runs Drupal core and which version it is on. On November 18, 2026, Drupal published SA-CORE-2026-017 (CVE-2026-132165), a critical installer flaw it rates 18 out of 25. Under specific conditions, an attacker can use install.php to try to reinstall Drupal, which can lead to a site takeover or remote code execution. The same releases also fix SA-CORE-2026-018 (CVE-2026-132166), a gadget chain Drupal says is not directly exploitable. Please update us to 11.4.13 (11.4.x), 11.3.22 (11.3.x) or 10.6.22 (10.6.x) today. If we are on an end-of-life version (11.2.x or below, 10.5.x or below, or Drupal 8 or 9), there is no official patch; please apply Drupal's steps for securing install.php and tell us how we can move to a supported release. After the update, please also follow that guide, confirm the version you left us on, and check for unexpected administrator accounts or changes to settings.php. Drupal's advisory does not report in-the-wild exploitation, and CISA's Known Exploited Vulnerabilities Catalog did not list either CVE when checked on November 18, 2026. EverThread does not test for this. Sources: SA-CORE-2026-017, SA-CORE-2026-018, securing the installer, CISA KEV.
Common questions
Does this mean my site was hacked?
No. A vulnerable version is a reason to update, secure the installer, and review the site. It is not proof of a break-in. Drupal's advisory does not report in-the-wild exploitation.
Can EverThread tell me if I am affected?
No. EverThread does not test for this. We cannot see whether your site runs Drupal, which version it is on, or whether install.php is reachable. A scan without a warning about this software does not mean your site is safe.
Which version should I install?
If you use Drupal 11.4.x, install 11.4.13. If you use 11.3.x, install 11.3.22. If you use 10.6.x, install 10.6.22. Those releases also include the fix for CVE-2026-132166. (SA-CORE-2026-017)
What if I am on an end-of-life version?
Drupal 11.2.x and below, 10.5.x and below, and Drupal 8 and 9 do not receive a patch. Follow Drupal's guide on securing install.php now, and plan to move to a supported release. (SA-CORE-2026-017)
Is this being exploited?
Drupal's advisory does not report exploitation on live sites. As of November 18, 2026, we found no report of in-the-wild exploitation of CVE-2026-132165 or CVE-2026-132166. CISA's Known Exploited Vulnerabilities Catalog (catalog version 2026.11.18) does not list either CVE. (SA-CORE-2026-017, CISA KEV)
What is the second advisory?
SA-CORE-2026-018 (CVE-2026-132166) is a moderately critical gadget chain in Drupal core, rated 14 out of 25 on Drupal's scale. Drupal says it is not directly exploitable and matters only if a separate vulnerability already lets an attacker pass unsafe input to unserialize(). The same updates that fix CVE-2026-132165 also fix this issue. (SA-CORE-2026-018)
Where can I follow updates?
Follow SA-CORE-2026-017, SA-CORE-2026-018, PSA-2026-11-16, Drupal's guide on securing install.php and CISA's Known Exploited Vulnerabilities Catalog. All current notices are on our notices page.
Security alerts by email
Hear about the next one first.
When a flaw puts websites at risk, we send one email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.
Sources
- Drupal core SA-CORE-2026-017, November 18, 2026: Drupal core - Critical - Remote code execution. CVE-2026-132165. Rated Critical 18 out of 25, AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon. Affected versions: less than 10.6.22, or 11.0.0 up to but not including 11.3.22, or 11.4.0 up to but not including 11.4.13. Describes the install.php reinstall condition, possible site takeover or remote code execution, the settings.php permission mitigation, Drupal Steward coverage of some but not all known attack vectors, fixed releases 11.4.13, 11.3.22 and 10.6.22, and that 11.2.x and below, 10.5.x and below, and Drupal 8 and 9 are end-of-life. If you cannot upgrade immediately, follow the instructions for securing the Drupal installer. Checked November 18, 2026. The advisory does not report in-the-wild exploitation.
- Drupal core SA-CORE-2026-018, November 18, 2026: Drupal core - Moderately critical - Gadget chain. CVE-2026-132166. Rated moderately critical 14 out of 25, AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:Uncommon. Same affected-version range and the same fixed releases as SA-CORE-2026-017. States that the issue is not directly exploitable and is mitigated because a separate vulnerability must allow an attacker to pass unsafe input to unserialize(). Checked November 18, 2026.
- Drupal PSA-2026-11-16, November 16, 2026: Upcoming critical Drupal core releases on November 18, 2026. Urged site owners to reserve time for core updates because exploits might be developed within hours or days. Listed supported branches 11.4.x, 11.3.x and 10.6.x, and also listed 12.0.0-beta3 and 11.5.0-beta1 as affected, with new beta or release candidate versions to follow the supported-branch updates. Checked November 18, 2026.
- Drupal.org, Securing the installer (install.php): Drupal Security Team documentation for blocking access to /core/install.php after installation. Linked from SA-CORE-2026-017 for sites that cannot upgrade immediately. Checked November 18, 2026.
- Drupal 11.4.13 release page, 11.3.22 release page and 10.6.22 release page: fixed releases named in the advisories. All three returned HTTP 200 when checked on November 18, 2026. We could not find a newer 12.0.0 or 11.5.0 beta or release candidate on Drupal.org at that check (12.0.0-beta4, 12.0.0-rc1, 11.5.0-beta2 and 11.5.0-rc1 returned HTTP 404).
- CISA Known Exploited Vulnerabilities Catalog: official JSON feed at catalog version 2026.11.18, 1,786 entries when checked on November 18, 2026. CVE-2026-132165 and CVE-2026-132166 were not listed.