Microsoft Security Advisory Details CVE-2026-111497 for .NET Brotli Vulnerability
A high-severity buffer overflow vulnerability in the .NET Brotli decompression library can allow unauthenticated attackers to corrupt process memory or cause information disclosure. The issue affects .NET 8, .NET 9, .NET 10, and .NET 11 packages, though default ASP.NET Core and HttpClient configurations are not inherently vulnerable unless Brotli decompression is explicitly enabled.
What changed From the source
A buffer overflow flaw identified as CWE-787 (Out-of-bounds Write) affects the Brotli decompression library used within .NET runtimes and NativeAOT packages. Tracked under CVSS version 3.1 with a high severity score of 8.1, the vulnerability permits an unauthenticated threat actor to read or corrupt process memory. Potential consequences include information disclosure, denial of service, or privilege elevation.
Default installations of ASP.NET Core and HttpClient do not automatically enable Brotli data decompression. Exposure occurs exclusively when developers explicitly turn on Brotli features or invoke specific compression APIs from System.IO.Compression such as BrotliStream or BrotliDecoder to handle untrusted, attacker-supplied payloads. .NET Framework remains unaffected by this advisory.
- CVSS 3.1 vector is set to AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C.
- Affected environments include all platforms and architectures utilizing vulnerable runtime or NativeAOT packages.
- Patched versions include 8.0.33 for .NET 8, 9.0.22 for .NET 9, 10.0.14 for .NET 10, and 11.0.0-rc.3.26522.148 for .NET 11.
At a glance · Security
What changedWhy it mattersWho should careUpgrade and migration considerations
Why it matters Analysis
Because memory corruption vulnerabilities can lead to arbitrary code execution or denial of service depending on the surrounding application logic, treating this high-severity advisory with urgency is critical. Systems that process external user uploads, web requests, or network responses via Brotli streams are at risk if they lack proper input validation or have automatic decoding handlers enabled.
The attack vector requires a combination of specific configuration choices and hostile payloads. Since default configurations disable automatic Brotli handling, many applications may have a lower immediate exposure surface unless custom settings explicitly opt into Brotli request or response decompression.
- Enabling automatic decompression features without strict oversight opens doors to wider denial-of-service vectors.
- Direct API consumers processing unverified byte arrays via
BrotliDecoderorBrotliStreamface direct memory safety risks.
Who should care Analysis
Engineering teams maintaining services on .NET 8, .NET 9, .NET 10, or .NET 11 must audit their codebases to determine if Brotli compression is active. Web APIs using ASP.NET Core request decompression with br support enabled, and backend services leveraging HttpClient handlers configured with DecompressionMethods.Brotli or DecompressionMethods.All, require immediate attention.
Developers utilizing NativeAOT or LLVM-backed runtimes should review the specific package manifests against the published vulnerability ranges to ensure proper updates are planned.
- Maintainers of high-throughput web gateways or microservices processing external HTTP traffic.
- Teams utilizing NativeAOT deployment models across Linux, Windows, macOS, and mobile targets.
Upgrade and migration considerations Analysis
Applying the official runtime and package updates remains the primary recommended remedy. However, if immediate patching is not feasible, temporary mitigations involve halting the processing of untrusted Brotli data or removing the br format from existing ASP.NET Core and HttpClient configurations.
Caution is advised when altering configuration snippets: developers should only modify existing decompression properties rather than introducing new configuration setups that could introduce secondary denial-of-service risks. All configuration adjustments must undergo thorough testing before deployment to prevent disruptions in normal request and response handling.
- Update runtime packages to version 8.0.33, 9.0.22, 10.0.14, 11.0.0-rc.3.26522.148, or later depending on the major .NET release.
- Ensure removal of the
brentry from ASP.NET Core request decompression or dropDecompressionMethods.Brotlifrom HTTP handlers as a temporary stopgap.
Sources and further reading
- Announcement dotnet/announcements#494 (original source)
Original: “Microsoft Security Advisory CVE-2026-111497 | .NET Brotli Decoder Out-of-bounds Write Vulnerability”, .NET Announcements, published 25 Oct 2026, retrieved 25 Oct 2026. This article was drafted with AI assistance from the official source and passed automated fact and quality checks. Spotted a mistake? See our corrections policy.