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 Moderately critical, 1 Less critical. Severity uses the official English labels and scores out of 25.
Tables scroll horizontally. In affected ranges, || means “or.” Fixes are advisory-specific; select the release appropriate to your branch.
Drupal Canvas
Machine name: canvas. 1 advisory this week.
| Official advisory / date | Severity | Affected versions | Fix / response |
|---|---|---|---|
| SA-CONTRIB-2026-006 ↗
CVE-2026-1553 2026-01-28 |
Moderately critical 10/25 | <1.0.4 |
1.0.4 ↗ |
SA-CONTRIB-2026-006 ↗ — Previously published Canvas pages may remain accessible after unpublishing; check access to unpublished pages.
Central Authentication System (CAS) Server
Machine name: cas_server. 1 advisory this week.
| Official advisory / date | Severity | Affected versions | Fix / response |
|---|---|---|---|
| SA-CONTRIB-2026-007 ↗
CVE-2026-1554 2026-01-28 |
Less critical 6/25 | <2.0.3 || >=2.1.0 <2.1.2 |
2.0.3 ↗ / 2.1.2 ↗ |
SA-CONTRIB-2026-007 ↗ — Authenticated users able to edit fields exported as CAS attributes can inject XML elements into authentication responses.
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-01-12
- Next published week: 2026-02-02