Latest / Decrypted: The UK Cyber Briefing / Drupal's critical code execution flaws: patch first, then count your modules
Transcript
- 0:03This is Decrypted. Monday, the nineteenth of October, twenty twenty-six.
- 0:09This is the morning edition.
- 0:11Drupal's critical code execution flaws: patch first, then count your modules.
- 0:19Drupal, the website platform, has patched two critical flaws that let an attacker run their own code on a
- 0:27server. That's remote code execution, or R C E, which means running your own code on someone else's machine.
- 0:35The project warns that working exploits could appear "within hours or days".
- 0:42N H S England Digital has already published its own alert, so this is on the UK radar.
- 0:50If you run Drupal, treat it as a patch-today story.
- 0:55So, what's actually broken?
- 0:59The main flaw is C V E twenty twenty-six, one zero eight zero nine seven, the public reference number for th
- 1:09is vulnerability. It sits in Field U I, the core module behind the admin screens where site builders define wh
- 1:18at a page contains. Drupal rates it critical, 19 out of 25 on its own scale.
- 1:25A second flaw, C V E twenty twenty-six, one zero eight zero nine nine, affects the contributed Entity List mo
- 1:36dule. It's fixed in version 3.
- 1:390.10. The detail matters.
- 1:43Drupal says core alone can't be exploited.
- 1:47Other add-on modules and custom code can expose the vulnerable function, and at least one known route needs n
- 1:55o login at all. Think of a building where the cleaners' cupboard has a weak lock.
- 2:01The cupboard is harmless until someone builds a corridor that opens onto it from the street.
- 2:06Whether your site has that corridor depends on which modules you installed years ago.
- 2:12Many teams couldn't list them from memory.
- 2:15So, what should you do, and in what order?
- 2:20The fixed releases are 10.
- 2:236.19, 11.3.19 and 11.4.10, depending on your branch.
- 2:31Older branches, including 11.
- 2:352.x and 10.5.x, get no fix.
- 2:40If you can't update straight away, Drupal says uninstalling the Field U I module protects you in the meantime
- 2:47. Its Drupal Steward service offers partial cover, but Drupal is explicit that updating is still necessary.
- 2:55For the defender, the awkward part is that there's no single signature to hunt for.
- 3:01Because the route in varies by site, you can't rely on one rule at the firewall.
- 3:07Review web logs for unexpected requests to admin and field paths since 14 October.
- 3:14Check for new files or accounts you didn't create.
- 3:17Nothing I've read reports confirmed exploitation, which is a window, not a reassurance.
- 3:25Now, what's the Secure by Design lesson here?
- 3:29Secure by Design asks the supplier to remove a class of risk, not leave it to every customer to defend.
- 3:37Here the dangerous function ships in core and waits for a module to expose it.
- 3:43A safer design would make that function refuse to run unless explicitly asked, so a careless add-on couldn't
- 3:50open the door. That's a supplier decision, and customers can't make it for them.
- 3:55What customers can control is how much surprise lives in their estate.
- 4:00The cost is modest and dull.
- 4:03A maintained list of every module on every site, a named owner for each site, and a rule that unsupported ver
- 4:11sions get retired rather than tolerated.
- 4:13If the honest answer to "who owns that site?
- 4:17" is "nobody", this week is when that gap costs money.
- 4:21Start with the sites nobody has touched in years.
- 4:25As always, this is opinion, not advice.
- 4:29That was Decrypted. The written version and every source are linked in the show notes.
- 4:36Thanks for listening.