
Microsoft Ships Out-of-Band .NET Fixes for Critical Brotli Flaw CVE-2026-111497
Microsoft released an out-of-band security update on October 25 for .NET 8, .NET 9, .NET 10 and .NET 11 Release Candidate 3.1 The release addresses a Brotli decoder out-of-bounds write that can let unauthenticated attacker-controlled input read or corrupt process memory.2
PATCH NOW IF EXPOSED • Reporting cutoff: October 27, 2026, 8:51 a.m. EDT / 12:51 UTC
The bottom line
Update exposed .NET workloads to 8.0.33, 9.0.22, 10.0.14 or .NET 11 RC3, then restart or redeploy the actual application.1 A stock .NET or ASP.NET Core installation is not exposed merely because the affected runtime is present: attacker-controlled Brotli data must reach an enabled decompression path.3
Verified facts
What happened
CVE-2026-111497 is an out-of-bounds write in the Brotli decoder. Microsoft says the .NET impact can include information disclosure, denial of service or elevation of privilege because an unauthenticated attacker may read or corrupt process memory.1 The upstream Google CNA record describes a broader potential outcome—including arbitrary code execution—for crafted Brotli streams reaching affected Google Brotli versions; that upstream CVSS v4 record scores the issue 9.2 Critical.5
The severity labels are not interchangeable. Microsoft’s MSRC page calls the maximum severity Critical while showing CVSS v3.1 8.1; the dotnet/runtime GitHub advisory labels its own CVSS v3.1 surface High at 8.1; and the Google CNA record uses CVSS v4 9.2 Critical.235
Why it matters
Exposure requires an affected .NET runtime or NativeAOT package and attacker-controlled Brotli data reaching one of these paths: ASP.NET Core request decompression with Brotli enabled, HttpClient automatic response decompression configured for Brotli, or direct use of BrotliStream, BrotliDecoder or another System.IO.Compression Brotli API.3 ASP.NET Core request decompression and HttpClient automatic response decompression are not enabled by default, and .NET Framework is not affected.1
| Deployment line | Affected range | Fixed target |
|---|---|---|
| .NET 8 | 8.0.0 through 8.0.32 | 8.0.33 |
| .NET 9 | 9.0.0 through 9.0.21 | 9.0.22 |
| .NET 10 | 10.0.0 through 10.0.13 | 10.0.14 |
| .NET 11 prerelease | Listed preview builds before RC3 | 11.0.0-rc.3.26522.148 |
The affected and patched ranges above come from Microsoft’s dotnet/runtime advisory.3
What this means for readers
- Inventory safely. Run
dotnet --list-runtimeson each host to see installed shared runtimes.1 Also inventory self-contained executables, containers and NativeAOT builds separately because they carry runtime components outside the shared host runtime.13 - Framework-dependent applications: install the fixed runtime for the targeted branch and restart the application so the updated runtime is loaded.1
- Self-contained and NativeAOT applications: rebuild, republish and redeploy with the patched SDK/runtime packages. Updating only the machine’s shared runtime does not replace a vulnerable decoder already bundled or linked into the executable.3
- Containers: rebuild and redeploy from updated .NET base images; do not treat a host-runtime update as proof that container images changed.1
- If patching is delayed: stop untrusted Brotli data from reaching enabled decompression paths, and test any configuration change because disabling decompression can alter normal request or response handling.3
What end users should know
This is primarily a developer and system-administrator update, not a reason to uninstall .NET blindly. On Windows, Microsoft says the .NET 8 update is available through Microsoft Update for client systems, WSUS or the Microsoft Update Catalog for Windows Server, and Visual Studio-managed installations should be updated through the Visual Studio Installer.4 Business users should let their IT provider confirm which applications bundle their own runtime before assuming Windows Update alone covered every deployment.
The out-of-band release includes other fixes
The October 25 release also fixes CVE-2026-114148 for affected Linux .NET tarballs and re-releases fixes for CVE-2026-70197 and CVE-2026-102870 because Microsoft says the October 13 release did not fully address those two issues.1 Those are separate vulnerabilities; this article’s exposure and remediation guidance focuses on the Brotli flaw.
What remains unknown
No active-exploitation claim. MSRC’s current page says “Exploited: No,” while rating exploitation more likely; that is a point-in-time vendor assessment, not proof that exploitation can never occur.2
Independent reporting reviewed by the cutoff likewise said no in-the-wild exploitation had been reported, while noting laboratory code-execution demonstrations were limited to tested configurations.6 Do not treat a crash, worker restart or the mere presence of .NET as proof of compromise.
Related coverage
Our earlier PHP Windows package advisory covers rebuilt PHP packages that embed Brotli. It is a different runtime and update path from Microsoft’s .NET out-of-band release.
Sources
- .NET October 2026 Out-of-Band Security Updates — Microsoft .NET Blog, October 25, 2026.
- CVE-2026-111497 Security Update Guide — Microsoft Security Response Center, released October 25 and updated October 26, 2026.
- Microsoft Security Advisory CVE-2026-111497 — .NET Brotli Decoder Out-of-bounds Write — dotnet/runtime on GitHub, October 25, 2026.
- .NET 8.0 Update — October 25, 2026 — Microsoft Support.
- CVE Record: CVE-2026-111497 — CVE Program / Google CNA, updated October 23, 2026.
- Node2Shell: Brotli Flaw Triggers Patching Across Microsoft, Node.js, Python Packages — SecurityWeek, October 26, 2026.
Update and correction note: This article reflects source status through October 27, 2026, 8:51 a.m. EDT. We will update it if Microsoft changes affected-version, exploitability or remediation guidance.
