DRUPAL-CORE-2026-014 CVE-2026-108097

A remote code execution vulnerability exists within the Field UI module in Drupal core.

Not rated yet Packagist

Severity: Not rated yet; No source has published a CVSS score yet
Exploit chance (EPSS): 0.33%; Chance of exploitation in the next 30 days. Higher than 25.74% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-470 Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Fix: 12.0.0-beta2; Upgrade drupal/core to this version or later

Description

The vulnerability is not directly exploitable with core alone, but multiple serious exploit paths exist with contributed modules. At least one known exploit path does not require authentication. Custom code may also expose the vulnerable functionality.

The vulnerability can be mitigated by uninstalling the core Field UI module (field_ui), which will provide protection while sites are updated.

Drupal Steward protection:

This issue is being protected by Drupal Steward. Sites that use Drupal Steward are already protected from some known attack vectors, but the protection offered will not cover all possible exploits. Sites should upgrade in the near future in case additional attack vectors are discovered.

Affected versions

Packagist

Package	Vulnerable	Fixed in
drupal/core	`>= 8.9.0, < 10.6.19` `>= 11.0.0, < 11.3.19` `>= 11.4.0, < 11.4.10` `>= 12.0.0-alpha1, < 12.0.0-beta2`	`10.6.19` `11.3.19` `11.4.10` `12.0.0-beta2`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

drupal/core Packagist → `12.0.0-beta2`

composer

composer require drupal/core:^12.0.0-beta2

Weakness

CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.

How to prevent it

Architecture and Design: Refactor your code to avoid using reflection.
Architecture and Design: Do not use user-controlled inputs to select and load classes or code.
Implementation: Apply strict input validation by using allowlists or indirect selection to ensure that the user is only selecting allowable classes or code.

References

Timeline

Oct 14, 2026 Published
Oct 30, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
DRUPAL-CORE-2026-004 Drupal Core has a SQL Injection issue	Critical Known exploited	Also affects drupal/core
CVE-2020-28949 Multiple vulnerabilities through filename manipulation in Archive_Tar	High Known exploited	Also affects drupal/core
CVE-2020-13671 Drupal core Unrestricted Upload of File with Dangerous Type	High Known exploited	Also affects drupal/core
CVE-2019-6340 Drupal Core Remote Code Execution Vulnerability	High Known exploited	Also affects drupal/core
CVE-2018-7602 Drupal Core Remote Code Execution Vulnerability	Critical Known exploited	Also affects drupal/core
CVE-2018-7600 Drupal Core Remote Code Execution Vulnerability	Critical Known exploited	Also affects drupal/core
DRUPAL-CORE-2026-016 The Navigation module doesn't sufficiently sanitize certain attributes, which can lead to a cross-site scripting (XSS) vulnerability.	Not rated yet	Also affects drupal/core
DRUPAL-CORE-2026-015 The Drupal core Link module provides a field type that can be used for internal and external URLs.	Not rated yet	Also affects drupal/core

Credits: Drew Webber (mcdruid), Octavio Galland (ogalland-tob)

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor