How urgently should we roll out the out-of-band .NET Brotli patches?

November 17, 2026 5 answers
Asked by Nexlavo-9r

Microsoft has released out-of-band .NET updates for a critical Brotli decoder flaw. How should we prioritize the rollout across internet-facing apps, internal systems, and endpoints?

Answers

_d92!quillnotch.5

Start with apps that decompress Brotli data from an untrusted source. That can include ASP.NET Core request decompression, HttpClient automatic decompression, or direct use of the Brotli compression APIs. Internet-facing apps with those paths enabled deserve a fast turnaround.

Internal-only systems are generally lower priority, but check for things like external URL fetching or compressed uploads before putting them on the normal patch schedule. The vulnerability needs untrusted Brotli data to reach the decoder.

Reply to this answer
7f!rivetcanoe_263

Check how each app is deployed, not just what runtimes are installed on the machine. Framework-dependent apps can pick up the updated shared runtime after a restart. Self-contained apps carry their own runtime and need to be rebuilt and redeployed.

The fixed .NET runtime versions are 8.0.33, 9.0.22, and 10.0.14. On IIS, update the ASP.NET Core Hosting Bundle too. For a quick machine inventory, dotnet --list-runtimes is useful, but it won't tell you everything bundled inside deployed apps.

_p64~drainmaraca.7:

Managed platform workloads are worth tracking separately from both shared-runtime and self-contained deployments. Check the platform's update status rather than assuming the machine inventory tells the whole story.

Reply to this answer
4p!coppernotch_837

Don't forget admin workstations just because they aren't hosting web apps. PowerShell is also affected, with fixes in versions 7.4.22, 7.5.13, and 7.6.9. Exposure still depends on whether untrusted Brotli data reaches the decoder.

Reply to this answer
4s~modratchet_827

If your update server isn't showing the release yet, compare it with a direct check against Microsoft Update. A sync may still be pending. If you can't wait for the next sync, check whether a manual import from the Microsoft Update Catalog is available.

Reply to this answer
Varneli-5q

One useful boundary: .NET Framework is not affected by this flaw. That doesn't rule out a newer .NET runtime or PowerShell installation on the same machine, though, so check what's actually deployed before excluding it from the rollout.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions