Drupal core critical security update (CVE-2026-108097)

What to do

• Check whether you use Pantheon Customer Sites. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d 5h it lasted.

  Anything that failed between 2026-10-14 17:52 UTC and 2026-10-15 23:11 UTC may need a replay.

• Subscribe to Pantheon's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=pantheon works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Pantheon 5

1. monitoringOct 14, 2026, 5:52 PM UTC

   A Drupal core security release is now available for CVE-2026-108097 (risk 19/25). It fixes a critical remote code execution vulnerability in the Field UI module. Drupal core alone is not directly exploitable, but several exploit paths exist through contributed modules, including at least one path that does not require authentication. Custom code can also expose the vulnerable functionality. Action required Update your Drupal sites to a patched release as soon as possible: Drupal 11.4.10 Drupal 11.3.19 Drupal 10.6.19 Drupal 12.0.0-alpha1 through 12.0.0-beta1 are also affected. See the Drupal security advisory for Drupal 12 remediation details. Drupal 11.2.x and earlier, Drupal 10.5.x and earlier, Drupal 9, and Drupal 8.9 are end-of-life. These versions are affected and do not receive security patches. Upgrade sites on these versions to a supported Drupal release. To apply the update, use the Drupal core update workflow in the Pantheon Dashboard. See the Pantheon security release note for instructions. Mitigation until you update If you cannot update immediately, uninstall the core Field UI module ( field_ui ). The Drupal Security Team states that this protects your site until you update. As a founding Platform Partner of the Drupal Steward program , Pantheon provides protection against some known attack vectors. Drupal Steward does not cover all possible exploits, so it does not replace updating your site.

   provider

2. monitoringOct 14, 2026, 7:49 PM UTC

   We are aware of the Drupal 7 release and will update this incident when it is available as an upstream update.

   provider

3. monitoringOct 14, 2026, 8:51 PM UTC

   Drupal 7.107 is now available as an upstream update. Customers running Drupal 7 applications should update to Drupal 7.107 as soon as possible. To apply the update, use the Drupal core update workflow in the Pantheon Dashboard.

   provider

4. monitoringOct 15, 2026, 7:17 PM UTC

   Drupal 10 and 11 security updates are available through Integrated Composer, and the Drupal 7.107 upstream security update has been released. Release notes are available for both update paths: Drupal core security update and Drupal 7.107 security update .

   provider

5. resolvedOct 15, 2026, 11:11 PM UTC

   Drupal Steward protection is in place for some known attack vectors related to CVE-2026-108097 . This reduces exposure, but does not cover every possible exploit path or replace applying the security update. No customer impact is currently reported, and we continue to monitor. Patched Drupal 10 and 11 releases are available through Integrated Composer, and Drupal 7.107 is available as an upstream update. Please update affected sites as soon as possible. If you cannot update immediately, uninstall the core Field UI module (field_ui) as a temporary mitigation. See the Drupal core security update and Drupal 7.107 security update for details.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.