Illustration of a closed white software box with a purple padlock on top and a blue shield in front

Drupal Critical Installer Flaw: Update to 11.4.13 Now

Admin

Drupal published security advisory SA-CORE-2026-017 on November 18, 2026, rated critical. Under specific conditions, the installer that ships with core can be used to attempt a reinstall of the site and take it over. It affects Drupal 10 and 11, and the fix is 11.4.13, 11.3.22 or 10.6.22.

What we know

  • The advisory: SA-CORE-2026-017, published by the Drupal Security Team on November 18 at 17:43 UTC. It is rated "Critical," 18 out of 25, for remote code execution, and tracked as CVE-2026-132165.
  • Where the flaw is: in install.php, the installer file included in every copy of Drupal. Per the advisory, under specific conditions someone without an account can use it to attempt to reinstall Drupal, which can lead to site takeover or code execution on the server.
  • What limits it: the advisory says some exploit paths are blocked if the web server can't write to settings.php or change its permissions. Drupal's own scoring rates the attack as complex and the vulnerable configuration as uncommon.
  • Is there exploit code? The advisory's score marks it as "Proof": by Drupal's definitions, a proof of concept exists. The advisory does not report active attacks.
  • Affected versions: everything before 10.6.22; 11.0.0 up to before 11.3.22; and 11.4.0 up to before 11.4.13. The November 16 pre-announcement (PSA-2026-11-16) also listed the 12.0.0-beta3 and 11.5.0-beta1 pre-releases.
  • Fixed versions: 11.4.13, 11.3.22 and 10.6.22, released on November 18. Per their release notes, they contain only security fixes.
  • A second advisory: the same releases fix SA-CORE-2026-018, "moderately critical" (14 out of 25, CVE-2026-132166). According to Drupal it isn't exploitable on its own; it only helps an attacker if the site already has a separate deserialization flaw.
  • No patch: Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 no longer receive fixes.
  • Who found it: the advisory credits Anthropic's open-source scanner. Sites on Drupal Steward were already protected from known attack paths, but Drupal still asks them to update.

What changes and what doesn't

The pre-announcement already said the issue was critical and that exploits could appear within hours or days. What's new is that the patch is out and the location of the problem is public. From now on, anyone can diff the old release against the new one.

There's one more change: Drupal now recommends blocking access to the installer on every site, including sites that are already patched. This is the second critical core fix in two months, after the Field UI flaw patched on October 14.

Sites built on other CMSs, such as WordPress, are not affected.

How to check if you're affected

  1. Check your version. In the Drupal admin: "Reports" → "Status report" (/admin/reports/status).
  2. Pick the release for your branch:

- 11.4.x → 11.4.13

- 11.3.x → 11.3.22

- 10.6.x → 10.6.22

- 11.2 or earlier, 10.5 or earlier, Drupal 8 or 9 → no patch: move to a supported branch and block the installer in the meantime.

  1. Update today, with a backup first. If your site is managed with Composer, each release page on drupal.org has the command. Then run database updates and clear the cache.
  2. Block the installer, whether or not you've updated. Drupal's official guide offers three ways: a deny rule in the web server config (Apache or nginx), a few lines in .htaccess if you're on shared Apache hosting, or a Composer script that deletes the file after each install. If you use Composer, note that core updates rewrite .htaccess, so those lines are lost unless you keep them separately, as the guide explains.
  3. Confirm it's blocked. Open your site's address followed by /core/install.php in a browser. It should return a 403 or 404 error. If you see the installer screen, it isn't blocked. Also check that your site and update.php still work.
  4. If someone else or your host maintains the site, ask them three things today: which Drupal version you're on, when it will be on 11.4.13, 11.3.22 or 10.6.22, and whether the installer is already blocked.
  5. If you're on Drupal 10, plan the move to Drupal 11: per the 10.6.22 release notes, the 10.6 branch gets security coverage until December 2026, when Drupal 11.5.0 is released.

Related: Drupal Fixes a Critical Core Flaw: Update to 11.4.10 Now

Sources

Updates: if Drupal reports attacks or ships a new release, it will be added here with a link.

Worried about how this affects your website?
We will go over what to change with you. It is a free 30-minute call.