Drupal security updates, week of 15 July 2026: Drupal core

Week of 15 July 2026

Drupal publishes security updates on Wednesdays. This week there was one, for Drupal core itself. Between them they carry 3 security fixes, because a module can fix several bugs in one update: Drupal core fixed 3.

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.

Drupal core

Moderately critical · Drupal core · every Drupal site · 3 security fixes

This is the underlying software that runs the entire website.

3 security fixes in one update. Drupal core fixed 3 separate security bugs this week: 2 cross site scripting, 1 information disclosure. One update covers all of them. The most serious, SA-CORE-2026-012, is explained here and the full list is at the end of the card.

A person with an ordinary account could put hidden code into the name of a layout block. If another person uses the layout editing screen, that code would run. This could let the first person see private information or change content on the site.

Who could do thisOnly someone with a login on your site.
Does it apply to youThis applies to sites where people use the layout editing screen.
Has it been used in attacksNo sign of it.
How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.

Tell your developerUpdate Drupal core to 11.4.4, 11.3.14 or 10.6.13, whichever branch you are on.

For developers: what the fix changed

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

The fix updates `core/modules/layout_builder/js/layout-builder.js` to use `textContent` instead of `innerHTML` when rendering the content preview placeholder label, preventing cross-site scripting.

Also in this release The release also includes fixes for two other vulnerabilities affecting the XSS utility and image style downloads, alongside version bumps.

11.4.3 to 11.4.4 4 commits, 8 files.

composer.lock +5 −5
composer/Metapackage/CoreRecommended/composer.json +2 −2
composer/Metapackage/DevDependencies/composer.json +1 −1
composer/Metapackage/PinnedDevDependencies/composer.json +2 −2
core/lib/Drupal.php +1 −1
core/lib/Drupal/Component/Utility/Xss.php +2 −0
core/modules/image/src/Controller/ImageStyleDownloadController.php +9 −9
core/modules/layout_builder/js/layout-builder.js +2 −2 fix

Full diff, 11.4.3 to 11.4.4 · Full diff, 11.3.13 to 11.3.14 · Full diff, 10.6.12 to 10.6.13

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

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

Moderately critical · Cross site scripting · SA-CORE-2026-012
Moderately critical · Cross site scripting · SA-CORE-2026-011
Moderately critical · Information disclosure · SA-CORE-2026-010

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 10 October 2026 as part of the archive back to January 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. In the archive the cards rated critical or above were read before publishing and the rest were checked by sampling. Install counts are today's, not the count on the day of the advisory.

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.

For context: I work mainly with UK charities, membership bodies 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.

Week of 15 July 2026

Moderately critical: 1 update

Drupal core

Send me your Drupal site's address.

Get in touch

Links

Reference