INTEREST JOURNAL DRUPAL & WEB

Drupal Security Updates: Week of 2026-05-21

About 400 words 2 min read

Japanese ↗
On this page

This week covers 1 Drupal core and 0 contributed-project advisories. Core ↗ and contributed ↗ notices are identified separately. Weeks run Monday–Sunday and article labels use Thursday.

This retrospective was compiled on November 4, 2026. Its title and organizational date do not represent an original publication date. Versions, severity and support status reflect the source as reviewed and may include subsequent corrections. Listed fixes are not necessarily the latest releases today; verify the current advisory, your release branch and Drupal compatibility before updating.

Advisory IDs and CVEs were rechecked against the official lists on November 5, 2026; core coverage and explicit CVE labels were added.

What to check first

No contributed-project advisory was found for this week in the reviewed list.

Tables scroll horizontally. In affected ranges, || means “or.” Fixes are advisory-specific; select the release appropriate to your branch.

Drupal core advisories

SA-CORE notices are grouped by the same week. Affected versions, integrations and permissions differ by advisory. Fix versions are historical records, not pinned update targets.

Official advisory / CVE Severity Affected versions Initial fixes
SA-CORE-2026-004 ↗
CVE-2026-9082
Highly critical 23/25 >= 8.9.0 < 10.4.10 || >= 10.5.0 < 10.5.10 || >= 10.6.0 < 10.6.9 || >= 11.0.0 < 11.1.10 || >= 11.2.0 < 11.2.12 || >= 11.3.0 < 11.3.10 11.3.10 ↗ / 11.2.12 ↗ / 11.1.10 ↗ / 10.6.9 ↗ / 10.5.10 ↗ / 10.4.10 ↗

SA-CORE-2026-004 ↗ — Unauthenticated PostgreSQL SQL injection; observed exploit attempts were recorded on May 22. Other databases still need upstream dependency fixes.

Administrator checklist

  1. Use composer show and the extension inventory to identify projects, release branches and enabled submodules. Distinguish installation from activation and compare the actual setup with each prerequisite.
  2. Back up the site and verify dependency and Drupal compatibility in staging before updating the appropriate branch. For unsupported projects, plan removal or replacement.
  3. Follow advisory-specific steps for database updates, cache rebuilds, permission review and token handling. Replacing package files may be only part of remediation.
  4. Test affected functionality as anonymous, ordinary and administrative users. Check the relevant content, files, APIs, payments or authentication paths; investigate possible earlier misuse separately through logs and records.

Weekly reviews

Drupal Security hub · 2026 weekly index

Official contributed-project advisory list ↗

Drupal Guide ↗