Runtime & Platform

Microsoft Issues October 2026 Out-of-Band Security Updates for .NET

Out-of-band security releases address multiple vulnerabilities affecting .NET 8, .NET 9, .NET 10, and .NET 11 Release Candidate 3. The patches resolve critical issues involving the Brotli decompression algorithm, Linux tarball ownership, and previous incomplete fixes.

What changed From the source

Microsoft has published out-of-band security updates for .NET 8, .NET 9, .NET 10, and .NET 11 Release Candidate 3. This release remediates CVE-2026-111497, which is a buffer overflow vulnerability inside the Brotli decompression algorithm impacting all platforms. Unauthenticated malicious actors might exploit this flaw to read or corrupt process memory, potentially resulting in information disclosure, denial of service, or privilege escalation.

The release also fixes CVE-2026-114148, a Linux-specific vulnerability concerning unsafe ownership metadata in .NET tarballs. This issue enables local attackers to alter files and escalate privileges. For .NET 10 and .NET 11, this affects source-build tarballs only, whereas for .NET 8 and .NET 9, it additionally impacts ASP.NET Core distributions acquired through ASP.NET Core tarballs, including users who do not build from source. Applications become vulnerable if they parse Brotli-compressed data using HttpClient automatic response decompression, ASP.NET Core request decompression, or System.IO.Compression Brotli APIs. Note that request and automatic response decompressions are disabled by default, and .NET Framework remains unaffected.

Furthermore, this release includes corrected fixes for CVE-2026-70197 regarding SocketAsyncEventArgs memory corruption in .NET 8, 9, 10, and 11, and CVE-2026-102870 concerning the Blazor WebAssembly debugger in .NET 10 and 11, as the previous October 13, 2026 patches were incomplete.

  • .NET 8 updated to version 8.0.33
  • .NET 9 updated to version 9.0.22
  • .NET 10 updated to version 10.0.14
  • .NET 11 updated to Release Candidate 3

At a glance · Runtime & Platform

What changedWhy it mattersWho should careUpgrade and migration considerations

Why it matters Analysis

The discovery of a buffer overflow in the Brotli decompression algorithm poses significant risks for services handling untrusted compressed payloads. Because Brotli is widely used for web traffic optimization, any flaw in its handling can expose server memory to unauthorized external readers or corrupt process states.

Additionally, the inclusion of tarball ownership fixes on Linux environments means supply chain and build infrastructure security is a priority for this patch cycle. The re-release of incomplete security advisories from earlier in the month highlights the urgency of validating that previous mitigations were fully integrated.

Who should care Analysis

Development and operations teams managing applications built on .NET 8, .NET 9, .NET 10, or .NET 11 Release Candidate 2 should apply these updates immediately. Organizations processing Brotli data streams via ASP.NET Core request decompression, HttpClient, or explicit compression APIs are directly exposed if those features are active.

Linux administrators utilizing source-build tarballs for .NET 10 and .NET 11, or ASP.NET Core tarballs for .NET 8 and .NET 9, must account for the tarball ownership vulnerability during their rebuild procedures.

Upgrade and migration considerations Analysis

Deployment strategies dictate how patches must be applied. Framework-dependent applications require updating the installed runtime on the host machine followed by a service restart. Self-contained applications bundle their runtimes and must be fully rebuilt and republished with the updated tooling, as updating the host runtime will not modify the bundled binaries.

Containerized workloads need to be rebuilt and redeployed utilizing the refreshed .NET container images. Source-build consumers must fetch updated artifacts to compile new packages, while ASP.NET Core tarball users on .NET 8 and .NET 9 need to refresh their specific runtime installations. Administrators can verify installed runtimes using the list runtimes command line utility, keeping in mind that self-contained and container deployments must be audited separately.

Sources and further reading

Original: “.NET October 2026 Out-of-Band Security Updates”, .NET Blog, 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.