The short version
- The flaw. CVE-2026-108097 sits in Drupal core's Field UI module, which builds the admin pages for managing fields. Drupal rates it 19 out of 25, its critical level, and shipped fixes on 14 October in 11.4.10, 11.3.19 and 10.6.19. Core alone does not expose it.
- How it is reached. Contributed modules provide exploit paths, at least one of which needs no authentication, and custom code may also expose the flawed functionality. The advisory does not name the contributed modules involved.
- Exposure. In the week starting 4 October, 151,442 of the 531,499 sites reporting their core version to drupal.org, or 28.5%, were on an affected branch that received no fix. Field UI is installed by Drupal's Standard install profile.
- Exploitation status. As of 15 October no public exploit code had surfaced and no attacks had been described. Drupal pre-announced the release on 12 October and told sites to reserve time for it because exploits might be developed quickly.
- A second module. The Entity List module has its own critical remote code execution advisory, CVE-2026-108099, with the same conditions including a no-login path. Its 3.0.10 release carries the fix, and updating core does not update the module.
Timeline
| Date | Event |
|---|---|
| 12 Oct | Drupal pre-announces the core release and tells sites to reserve time for it, warning that exploits might be developed within hours or days. |
| 14 Oct | Fixes ship in Drupal 11.4.10, 11.3.19 and 10.6.19. |
| 15 Oct | No public exploit code for CVE-2026-108097 has surfaced, and no attacks using it are described. |
| 19 Oct | Drupal's warning of fast exploitation risk is reported, with no mention of in-the-wild exploitation. |
What the bug is and what the fix changed
Field UI builds its admin tables from render arrays, the PHP arrays Drupal turns into HTML. Before the fix, the table element's pre-render step ran whatever PHP callable each row carried in its #region_callback property, through call_user_func_array, without checking what that callable was.
Drupal's renderer has refused to run untrusted render callbacks since version 8.8 in 2019. It trusts the table element's own methods, so the pre-render step ran and the check never reached the callable it then executed. The 11.4.10 code no longer calls the callback; it reads each row's region from the row's own region value and falls back to the table's hidden or first region. The same call had been in the code since at least Drupal 8.9.0 in 2020.
Custom code that set #region_callback on a field_ui_table row will find it no longer runs after the update. Pantheon tells sites to check such code and to test the manage fields and manage display pages after updating.
Who is affected and what to run
The fixed releases are 11.4.10, 11.3.19 and 10.6.19; 12.0.0-beta2 carries the fix but is not for production use. No fix exists for 11.2.x and below, 10.5.x and below, or Drupal 8 and 9, all end-of-life. Both 11.3.x and 10.6.x lose security coverage in December 2026.
A site that cannot update yet can uninstall the field_ui module, which the advisory says will provide protection while sites are updated; the field management admin pages are unavailable while it is removed. Drupal Steward, a web application firewall service run for customers by Acquia, Pantheon, Ironstar and Skpr, already blocks some known attack vectors but not all, and those sites should still update.
Entity List is fixed separately in 3.0.10, and 90 sites reported using it in the week starting 4 October. The same core releases also fix cross-site scripting flaws in the Link module (CVE-2026-108515) and the Navigation module (CVE-2026-108514), both needing at least a logged-in user. Drupal 7 reached end of life on drupal.org in January 2025, but Pantheon says its long-term support with Tag1 Consulting shipped Drupal 7.107 with a backport of the fix.
Exploitation risk so far
Neither the advisory nor public reports described attacks using the flaw as of 15 October, and no publicly available exploit code had appeared. Drupal rated the flaw as having no public exploit code at the time of publication.
The project's warning about fast exploitation has recent precedent. In May, Drupal reported exploit attempts within two days of its advisory for a core SQL injection flaw that affected only sites on PostgreSQL, and CISA added that flaw to its catalogue of exploited vulnerabilities.
What is not known yet
- Which contributed modules open an exploit path to the Field UI flaw, and how widely they are deployed.
- Whether anyone has exploited CVE-2026-108097 since 15 October, when the sources last state that no exploit code or attacks were known.
- How many of the sites on affected, unfixed branches have updated since 14 October.
- How much custom code in the field sets #region_callback, and whether that code remains exposed after patching.
What to do
If you run Drupal
- Update to 11.4.10 for the 11.4.x branch, or to 11.3.19 or 10.6.19 for those branches, and plan to move off 11.3.x and 10.6.x before security coverage ends in December 2026.
- If you cannot update yet, uninstall the field_ui module and accept that field management admin pages will be unavailable.
- Update the Entity List module to 3.0.10 separately, since the core update does not cover it.
- Search custom code for #region_callback on field_ui_table rows and retest the manage fields and manage display pages after updating.
If you rely on Drupal Steward or a host that runs it
- Treat the firewall rules as partial cover only and still apply the core update; the advisory says Steward does not block every possible exploit.
For everyone else
- Keep an inventory of the exact versions of core and contributed modules in use, so a critical core advisory can be triaged against real exposure rather than against a branch name.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.