This week covers 0 Drupal core and 2 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
Contributed projects account for 2 advisories across 2 projects: 1 Critical, 1 Moderately critical. Severity uses the official English labels and scores out of 25.
Check these higher-rated issues first, then prioritize according to actual configuration, exposure and permissions.
- Unpublished Node Permissions — SA-CONTRIB-2026-029 ↗ , Critical 15/25. Access restrictions are inconsistently enforced for translations of unpublished nodes.
Tables scroll horizontally. In affected ranges, || means “or.” Fixes are advisory-specific; select the release appropriate to your branch.
Unpublished Node Permissions
Machine name: unpublished_node_permissions. 1 advisory this week.
| Official advisory / date | Severity | Affected versions | Fix / response |
|---|---|---|---|
| SA-CONTRIB-2026-029 ↗
CVE-2026-4933 2026-03-11 |
Critical 15/25 | <1.7.0 |
8.x-1.7 ↗ |
SA-CONTRIB-2026-029 ↗ — Access restrictions are inconsistently enforced for translations of unpublished nodes.
AI (Artificial Intelligence)
Machine name: ai. 1 advisory this week.
| Official advisory / date | Severity | Affected versions | Fix / response |
|---|---|---|---|
| SA-CONTRIB-2026-028 ↗
CVE-2026-3573 2026-03-11 |
Moderately critical 11/25 | <1.1.11 || >=1.2.0 <1.2.12 |
1.1.11 ↗ / 1.2.12 ↗ |
SA-CONTRIB-2026-028 ↗ — Previewing generated markup can expose confidential material from LLM requests in affected AI submodules.
Administrator checklist
- Use
composer showand the extension inventory to identify projects, release branches and enabled submodules. Distinguish installation from activation and compare the actual setup with each prerequisite. - Back up the site and verify dependency and Drupal compatibility in staging before updating the appropriate branch. For unsupported projects, plan removal or replacement.
- Follow advisory-specific steps for database updates, cache rebuilds, permission review and token handling. Replacing package files may be only part of remediation.
- 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
- Previous published week: 2026-03-02
- Next published week: 2026-03-16