Broccoli2Shell: When Patching the Server Doesn't Fix the App

Broccoli2Shell: When Patching the Server Doesn't Fix the App

•

Episode description

Broccoli2Shell: When Patching the Server Doesn’t Fix the App

A Microsoft out-of-band update for CVE-2026-111497 highlights a frustrating gap in business IT maintenance. The Brotli compression flaw affects .NET runtimes, Node.js, and other platforms, but patching the host server doesn’t automatically fix self-contained applications or containerised workloads. Noel Bradford walks through what the vulnerability actually does, why one shared component means multiple suppliers fixing on separate timetables, and how bundled runtimes can sit unchanged inside applications long after the underlying server receives its updates. Using the example of a small Horsham firm whose booking app could remain vulnerable despite monthly server patching, the episode makes the case for asking suppliers four specific questions: which systems contain the flaw, what can reach it, who owns each fix, and how will you prove the live application now runs the corrected component. The episode closes with a reminder that green ticks on infrastructure reports mean very little if nobody checks whether the software customers actually use received the update.

Chapters

  • Cold Open A server can be patched and an application supported, yet vulnerable code remains exactly where it was, still running and still wearing a green tick on someone’s report.
  • What the Vegetable Actually Does CVE-2026-111497 sits in the Brotli decompression routine. A specially crafted compressed stream can write past allocated memory, risking code execution if an application processes attacker-controlled Brotli data.
  • One Flaw, Lots of Copies Google, Node.js, and Microsoft each ship fixes for their own copy of Brotli on separate timetables. For .NET, affected versions are 8.0, 9.0, 10.0, and 11 preview; .NET Framework is unaffected, and automatic decompression is off by default.
  • The Patch That Never Reached the App Self-contained deployments and containers carry their own runtime. Updating the server does nothing for them. A Horsham heating firm could receive monthly green reports while its booking app still runs an unchanged, bundled runtime from the original publish date.
  • It Can Arrive with the Reply Outgoing connections still bring data back. Any feature that fetches external resources and decompresses the reply could reach a vulnerable decoder, regardless of firewall rules for incoming ports.
  • Please Spare Us the Apocalypse Sales Pitch Red Hat rates the flaw important with no public reliable proof of concept for remote code execution. An independent site reports a public crash PoC and one team achieving code execution without publishing method. No attacks reported in the wild as of 22 October.
  • The Questions That Earn Their Keep Four supplier questions: Have you assessed our systems for CVE-2026-111497? Which contain an affected component that can process external Brotli data? Who owns each fix and when will it deploy? How will you prove the live application runs the corrected component?
  • The Payoff The server can be updated, the supplier aware, and the ticket closed, yet the application customers and staff depend on may remain unchanged. Evidence must show the fix reached the thing we actually run.

Links

No chapters are available for this episode.