Threat researchCisent
A Drupal site has two critical flaws to patch: its core's, and PHP's, which are already being exploited
The United States confirmed that October's critical PHP flaws are being exploited, and Drupal, which runs on PHP, had fixed a critical flaw in its own core.

On October 26, 2026, CISA, the US cybersecurity agency, added to its catalog of exploited vulnerabilities the two critical flaws PHP fixed on October 21, CVE-2026-109618 and CVE-2026-109619.1 They allow code to run on the server without logging in, and we covered them here. A Drupal site, which runs on PHP, also has a critical flaw of its own: the one Drupal fixed in its core on October 14.2
PHP: already being exploited
CISA’s catalog lists the vulnerabilities known to be used in attacks, and since October 26 it includes the two PHP flaws.1 The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.3
Updating Drupal does not update PHP. The PHP version is managed by whoever runs the server or by the hosting provider, so the first question is who maintains it.
Drupal: a critical flaw in its core
Advisory SA-CORE-2026-014 describes a flaw in Field UI, a module that ships with Drupal core, that allows code to run on the server (CVE-2026-108097). Drupal rates it critical, 19 out of 25 on its risk scale.2
The flaw cannot be exploited with core alone: according to the Drupal team, there are several serious paths through contributed modules, and at least one does not require logging in. A site’s own code can also expose it.2 The advisory does not say which modules those are.
The fixed versions are 11.4.10, 11.3.19 and 10.6.19. Drupal 11.2 and earlier, 10.5 and earlier, and Drupal 8 and 9 no longer receive security fixes.2 If updating right away isn’t possible, uninstalling the Field UI module protects the site in the meantime.2 Drupal also fixed a similar flaw in Entity List, a contributed module, in its version 3.0.10.4
As of October 26, the Drupal core flaw is not in CISA’s catalog.1 When it fixed the flaw, the Drupal team warned that exploits could appear “within hours or days.”4
Why it matters
A Drupal site rests on three layers: the web server, PHP and Drupal. In October, all three got critical patches: if the server is nginx, F5 fixed five flaws on October 14, three of them critical, which we also covered.5
Each layer is updated by someone different: Drupal, by the site’s team; PHP and the web server, by whoever runs the server or by the hosting provider. One being up to date says nothing about the others.
Where Cisent comes in
An outdated PHP or Drupal on a server nobody checks is the kind of gap worth finding before an attacker does.
Sentinel Red Team attacks the organization’s systems with its authorization and within the scope it defines, to find the gaps before an attacker does: the admin panel exposed on a server nobody watches, the service published by mistake, the insecure configuration. It’s ongoing testing, not one audit a year, and every new attack pattern helps train the defense.
Sources
CISA, Known Exploited Vulnerabilities Catalog, version 2026.10.26, October 26, 2026: it added CVE-2026-109618 and CVE-2026-109619 that day, and CVE-2026-108097 is not listed. https://www.cisa.gov/known-exploited-vulnerabilities-catalog↩︎
Drupal Security Team, “Drupal core - Critical - Remote code execution - SA-CORE-2026-014”, October 14, 2026. https://www.drupal.org/sa-core-2026-014↩︎
PHP security team, security releases PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, October 21, 2026. https://www.php.net/archive/2026.php↩︎
BleepingComputer, “Drupal patches critical RCE flaws, warns exploits may emerge soon”, October 17, 2026. https://www.bleepingcomputer.com/news/security/drupal-patches-critical-rce-flaws-warns-exploits-may-emerge-soon/↩︎
F5, “Out-of-band Security Notification (October 14, 2026)”, K000163408. https://my.f5.com/manage/s/article/K000163408↩︎