Drupal security updates, in plain English

Week of 18 November 2026

Drupal publishes security updates on Wednesdays. On 18 November 2026 there was one, for Drupal core itself. Between them they carry 2 security fixes, because a module can fix several bugs in one update: Drupal core fixed 2.

One is for Drupal core. That applies to every Drupal site, so start there.

Each card says what the module does, what went wrong, who could do it, whether it applies to you, how urgent it is, and the one line to send to your developer. Worst rated first, and most used first within a rating.

New here? How Drupal security updates work explains who publishes these, why they matter and what the ratings mean. Earlier weeks and a search by module are on the main page.

Critical: 1 update

Cyber Essentials expects a fix within 14 days. Do it this week.

Drupal core

Critical · Drupal core · every Drupal site · 2 security fixes

This is the underlying software that runs the entire website.

2 security fixes in one update. Drupal core fixed 2 separate security bugs at once: 1 remote code execution, 1 gadget chain. One update covers all of them. The most serious, SA-CORE-2026-017, is explained here and the full list is at the end of the card.

The software includes a file used to set up the website initially. Someone without an account could use this file to try to set up the website again. This could allow them to view private user details or alter the underlying code, and there is no information they could not read or change.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youA site is affected under specific conditions that allow the setup file to be used again.
  • Has it been used in attacksA working example has been published, so assume someone will try.
  • How urgentDrupal rates this critical. Cyber Essentials expects a fix within 14 days. Do it this week.

Tell your developerUpdate Drupal core to 11.4.13, 10.6.22 or 11.3.22, whichever branch you are on.

For developers: what the fix changed

This release carries 2 security fixes. The summary below is for SA-CORE-2026-017, the most serious of them.

The fix secures the Drupal installer by adding a session token check in `install_bootstrap_full` to ensure only the initiating browser session can continue the installation, and by preventing reinstallation if `install_time` is already set in `install_begin_request`. It also stops automatically fixing file permissions during requirements checks in `install_check_requirements`.

Also in this release The release also includes a fix for SA-CORE-2026-018 (adding type checks and preventing unserialization in cache classes) and version bumps.

11.4.12 to 11.4.13 4 commits, 7 files.

  • composer.lock +5 −5
  • composer/Metapackage/CoreRecommended/composer.json +1 −1
  • composer/Metapackage/PinnedDevDependencies/composer.json +1 −1
  • core/includes/install.core.inc +53 −14 fix
  • core/lib/Drupal.php +1 −1
  • core/lib/Drupal/Core/Cache/CacheCollector.php +15 −0
  • core/lib/Drupal/Core/Discovery/YamlCacheCollectorDiscovery.php +9 −0

Full diff, 11.4.12 to 11.4.13 · Full diff, 10.6.21 to 10.6.22 · Full diff, 11.3.21 to 11.3.22

The comparison is against the release immediately before the fix. If your site is on an older release, more will have changed.

All 2 security bugs this update fixes, worst first. Each link is the drupal.org notice for that one.

Not sure what your site is running?

Send me your Drupal site's address.

I'll tell you what I can see from outside, what the Drupal 10 end of life on 9 December means for it, and what it would cost to have me keep it patched. There's no charge for that and no obligation. peter@peterbrady.co.uk

Compiled 19 November 2026 from the advisories published by the Drupal security team on drupal.org. The facts on each card are theirs. The plain English is mine, with help from a language model, and read before publishing.


Get in touch

Tell me who you are, what your organisation does, and what you need. That might be a Drupal site that needs looking after, an upgrade to get done before December, or an agency that needs Drupal cover.

If I can help, I'll say so and suggest a call. If I can't, I'll tell you straight away rather than waste your time.

peter@peterbrady.co.uk

For context: I work mainly with UK membership bodies, charities and research organisations, and with the agencies that look after their websites. Not recruiters.

Or start smaller and connect with me on LinkedIn. That's where I post what I find digging around in charity and grants data, and where the free tools turn up first.