Quick answers
- Is CVE-2026-108097 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108097 being exploited in the wild.
- How severe is CVE-2026-108097?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Drupal Core 8.9.0 to 10.6.18, 11.0.0 to 11.3.18, 11.4.0 to 11.4.9, 12.0.0-alpha1 to 12.0.0-beta1; drupal/core (Packagist) ECOSYSTEM:introduced=8.9.0,fixed=10.6.19|ECOSYSTEM:introduced=11.0.0,fixed=11.3.19|ECOSYSTEM:introduced=11.4.0,fixed=11.4.10|ECOSYSTEM:introduced=12.0.0-alpha1,fixed=12.0.0-beta2.
- Is there a fix for CVE-2026-108097?
- Yes. drupal/core (Packagist): upgrade to 10.6.19 or later. Until then: Uninstall the core Field UI module (field_ui) to mitigate the vulnerability while awaiting updates. Alternatively, sites using Drupal Steward are protected from some known attack vectors, though not all possible exploits. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108097 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-108097?
- Check whether you run Drupal Core or drupal/core (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- drupal/core (Packagist): upgrade to 10.6.19 or later
composer require drupal/core:^10.6.19
Uninstall the core Field UI module (field_ui) to mitigate the vulnerability while awaiting updates. Alternatively, sites using Drupal Steward are protected from some known attack vectors, though not all possible exploits.
Technical details
The vulnerability exists in Drupal Core's Field UI module and is not directly exploitable in isolation, but multiple serious attack paths exist when combined with contributed modules or custom code. At least one documented exploit path does not require authentication, making it accessible to unauthenticated attackers over the network. The flaw allows for remote code execution, potentially granting complete control over affected installations.
Affected products
- Drupal Core 8.9.0 to 10.6.18, 11.0.0 to 11.3.18, 11.4.0 to 11.4.9, 12.0.0-alpha1 to 12.0.0-beta1
Identifiers
- CVE-2026-108097
- DRUPAL-CORE-2026-014
Timeline
- 2026-10-14: disclosed