INTEREST JOURNAL DRUPAL & WEB

Drupal Security Updates: Week of 2026-06-18

About 800 words 4 min read

Japanese ↗
On this page

This week covers 5 Drupal core and 3 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 3 advisories across 3 projects: 3 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.

  • Formatter Field — SA-CONTRIB-2026-048 ↗ , Critical 19/25. Serialized formatter settings permit object injection when an editor can write raw field values through JSON:API or another path.
  • Flag attendance field — SA-CONTRIB-2026-049 ↗ , Critical 19/25. Serialized attendance data allows object injection for users able to edit the entity and directly write its field values.
  • Plotly.js Graphing — SA-CONTRIB-2026-050 ↗ , Critical 19/25. Serialized graph data permits object injection if an editor can submit raw field values, including through writable JSON:API.

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

Flag attendance field

Machine name: flag_attendance_field. 1 advisory this week.

Official advisory / date Severity Affected versions Fix / response
SA-CONTRIB-2026-049 ↗
CVE-2026-55809
2026-06-17
Critical 19/25 <1.2 8.x-1.2 ↗

SA-CONTRIB-2026-049 ↗ — Serialized attendance data allows object injection for users able to edit the entity and directly write its field values.

Formatter Field

Machine name: formatter_field. 1 advisory this week.

Official advisory / date Severity Affected versions Fix / response
SA-CONTRIB-2026-048 ↗
CVE-2026-12535
2026-06-17
Critical 19/25 <2.0.0 2.0.0 ↗

SA-CONTRIB-2026-048 ↗ — Serialized formatter settings permit object injection when an editor can write raw field values through JSON:API or another path.

Plotly.js Graphing

Machine name: plotly_js. 1 advisory this week.

Official advisory / date Severity Affected versions Fix / response
SA-CONTRIB-2026-050 ↗
CVE-2026-55810
2026-06-17
Critical 19/25 <3.0.2 3.0.2 ↗

SA-CONTRIB-2026-050 ↗ — Serialized graph data permits object injection if an editor can submit raw field values, including through writable JSON:API.

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-005 ↗
CVE-2026-55803
Critical 18/25 <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || 11.0.* || 11.1.* 11.3.12 ↗ / 11.2.14 ↗ / 10.6.11 ↗ / 10.5.12 ↗
SA-CORE-2026-006 ↗
CVE-2026-55804
Moderately critical 14/25 <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || 11.0.* || 11.1.* 11.3.12 ↗ / 11.2.14 ↗ / 10.6.11 ↗ / 10.5.12 ↗
SA-CORE-2026-007 ↗
CVE-2026-55806
Less critical 9/25 <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || 11.0.* || 11.1.* 11.3.12 ↗ / 11.2.14 ↗ / 10.6.11 ↗ / 10.5.12 ↗
SA-CORE-2026-008 ↗
CVE-2026-55807
Moderately critical 10/25 <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || 11.0.* || 11.1.* 11.3.12 ↗ / 11.2.14 ↗ / 10.6.11 ↗ / 10.5.12 ↗
SA-CORE-2026-009 ↗
CVE-2026-55808
Moderately critical 11/25 <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || 11.0.* || 11.1.* 11.3.12 ↗ / 11.2.14 ↗ / 10.6.11 ↗ / 10.5.12 ↗

SA-CORE-2026-005 ↗ — PHP object injection requires writable JSON:API and an unusual serialized reference field; shipped core field types do not meet those conditions.

SA-CORE-2026-006 ↗ — A gadget chain becomes useful to an attacker when a separate unsafe unserialize path exists.

SA-CORE-2026-007 ↗ — Incorrect Host validation in rebuild.php can allow cache poisoning or external redirects.

SA-CORE-2026-008 ↗ — Media oEmbed URL discovery enables SSRF and requires an explicit trusted-host configuration when used.

SA-CORE-2026-009 ↗ — JSON:API and REST image uploads validate extensions without sufficiently checking MIME types.

Sites using oEmbed URL discovery also need media_oembed_discovery_trusted_host_patterns in settings.php; distinguish these from providers.json-based setups.

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 ↗