INTEREST JOURNAL DRUPAL & WEB

Drupal Core Releases: Week of 2026-04-16

About 700 words 4 min read

Japanese ↗
On this page

This review covers 4 releases dated 2026-04-13–2026-04-19 from Drupal’s official release list ↗ . Weeks run Monday to Sunday using the official Created on date in UTC; Thursday supplies the article label. Japanese notification dates can differ.

This retrospective reflects sources reviewed on November 4, 2026, including later corrections and regression warnings. The article’s organizational date is not a claim of earlier publication. Historical release numbers are not current upgrade recommendations; check current official guidance before updating.

This week’s releases

This week has 4 stable releases and 0 prereleases. Security labels and explicitly linked fixed advisories are tracked separately.

Status flags reflect the source at review time. Insecure can mark a release superseded by later fixes, not necessarily its original status. Absence of a flag is not a security guarantee. Tables scroll horizontally.

Release Created on (UTC) Type Flags at review
10.5.9 ↗ 2026-04-15 Stable / Security update Insecure
10.6.7 ↗ 2026-04-15 Stable / Security update Insecure
11.2.11 ↗ 2026-04-15 Stable / Security update Insecure
11.3.7 ↗ 2026-04-15 Stable / Security update Insecure

Stable releases

Drupal 10.5.9

Official release notes ↗ · 15 Apr 2026 at 17:57 UTC

Security fixes cover Ajax modal XSS and a gadget chain requiring a separate unsafe-deserialization flaw. Composer 2.9.7 supplies additional hardening.

Update/testing notes: Choose the fixed release for the installed branch. The gadget-chain advisory does not describe a directly exploitable standalone flaw.

Advisories explicitly listed as fixed: SA-CORE-2026-001 ↗ , SA-CORE-2026-002 ↗ .

Further references linked by the release notes:

Drupal 10.6.7

Official release notes ↗ · 15 Apr 2026 at 17:56 UTC

Security fixes cover Ajax modal XSS and a gadget chain requiring a separate unsafe-deserialization flaw. Composer 2.9.7 supplies additional hardening.

Update/testing notes: Choose the fixed release for the installed branch. The gadget-chain advisory does not describe a directly exploitable standalone flaw.

Advisories explicitly listed as fixed: SA-CORE-2026-001 ↗ , SA-CORE-2026-002 ↗ .

Further references linked by the release notes:

Drupal 11.2.11

Official release notes ↗ · 15 Apr 2026 at 17:54 UTC

Security fixes cover Ajax modal XSS and a gadget chain requiring a separate unsafe-deserialization flaw. Composer 2.9.7 supplies additional hardening.

Update/testing notes: Choose the fixed release for the installed branch. The gadget-chain advisory does not describe a directly exploitable standalone flaw.

Advisories explicitly listed as fixed: SA-CORE-2026-001 ↗ , SA-CORE-2026-002 ↗ .

Further references linked by the release notes:

Drupal 11.3.7

Official release notes ↗ · 15 Apr 2026 at 17:51 UTC

The revised notes warn of a configuration-import regression that can cause data loss. Version 11.3.7 additionally includes core security fixes.

Update/testing notes: The notes direct users to 11.3.8. If configuration was imported on 11.3.6 or 11.3.7, follow its re-import and data checks. Verify current upgrade targets separately.

Advisories explicitly listed as fixed: SA-CORE-2026-001 ↗ , SA-CORE-2026-002 ↗ , SA-CORE-2026-003 ↗ .

Further references linked by the release notes:

Core security advisories

These SA-CORE notices concern Drupal core, distinct from contributed-project SA-CONTRIB notices. Not every listed release is affected by every issue; follow the per-release links and each advisory’s ranges.

  • SA-CORE-2026-001 ↗ — Critical 15/25: Ajax modal options can introduce script injection. CVE: CVE-2026-6365
  • SA-CORE-2026-002 ↗ — Moderately critical 14/25: A gadget chain requires a separate unsafe-deserialization flaw; it is not directly exploitable alone. CVE: CVE-2026-6366
  • SA-CORE-2026-003 ↗ — Moderately critical 13/25: Stored XSS through CKEditor link suggestions in the 11.3 feature. CVE: CVE-2026-6367

Update checks

  1. Identify the installed branch, PHP, database and dependencies, then choose a supported target. Historical release numbers are not instructions to pin to those versions.
  2. Back up and test in staging. Read official update steps, known issues and required configuration changes.
  3. Follow your deployment process for database updates and cache rebuilds after Composer changes. Review configuration differences, editing flows, public output and custom features.
  4. Whether a user-guide explanation needs revision will be assessed separately. This review organizes release evidence; it does not modify the guide or claim runtime verification.

Drupal Releases · 2026 weekly index

Drupal Guide ↗