Scan my site freeScan free

Security notices / Drupal core installer CVE-2026-132165, rated 18 out of 25, November 18, 2026: site takeover or remote code execution, update to 11.4.13, 11.3.22 or 10.6.22

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.

Last updated: Wednesday, November 18, 2026, 4:33 PM ETStatus: Fix released. Update to 11.4.13, 11.3.22 or 10.6.22.

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

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

  1. 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)
  2. 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)
  3. 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)
  4. 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)
  5. 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.php or 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.

We email you a link to confirm first, and every alert has a one-click unsubscribe. Alerts can include a short note about EverThread. Already a customer? Use your account email and your alerts include a link to your dashboard. Privacy

Sources

While you are here

Check your site's other basics free. We look at your home page the way a browser does. This scan cannot see whether your site runs Drupal, which version it is on, or whether the installer is reachable. No account.

Or sign up free and we check it every day and email you when something changes.