DRUPAL-CORE-2026-014 in drupal/core
Published 14 Oct 2026 · Updated 14 Oct 2026
Affected package
- Affected
- >=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
- Fixed in
- 10.6.19, 11.3.19, 11.4.10, 12.0.0-beta2
composer require drupal/core:^12.0.0-beta2Details
A remote code execution vulnerability exists within the Field UI module in Drupal core.
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.
Is DRUPAL-CORE-2026-014 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.