Microsoft released its November 2026 servicing updates for .NET on November 10, 2026. The new builds are .NET 10.0.15, .NET 9.0.23 and .NET 8.0.34, alongside the first general release of .NET 11.0.0 with SDK 11.0.100. Together the advisories cover 25 CVEs in the runtime, ASP.NET Core and the Visual Studio tooling.
The timing makes this month's patches unusual. .NET 8 and .NET 9 reached end of support on the same day, so these are the final fixes those two versions will get. Any vulnerability found from now on will only be patched in .NET 10 and .NET 11.
What the Updates Fix
Microsoft's summary table lists 25 CVEs. Most of them land in ASP.NET Core, the web framework, but the base .NET runtime and the Visual Studio tooling are also affected. Grouped by the type of flaw, the list breaks down as follows:
- Nine denial of service issues, six in ASP.NET Core and three in .NET itself.
- Six elevation of privilege flaws, four in ASP.NET Core and two in .NET.
- Five remote code execution issues, all listed under Visual Studio.
- Three security feature bypass problems, two in ASP.NET Core and one in .NET.
- Two information disclosure bugs in ASP.NET Core.
The post groups these by advisory and points to the full details for each one. Microsoft's own advisories remain the place to check exact affected packages and any extra steps.
Which Versions Are Affected
The spread across versions is wide. Of the 25 CVEs, 17 apply to .NET 8 and most of those also reach .NET 9, .NET 10 and .NET 11. That means the same bugs have lived in the code base for several releases.
Seven CVEs apply only to .NET 11, including an ASP.NET Core elevation of privilege flaw and a .NET security feature bypass. Because those fixes are already in the 11.0.0 build, teams adopting the new release today get them by default. One ASP.NET Core denial of service fix applies only to .NET 8.
Several flaws, such as CVE-2026-114146 in ASP.NET Core and CVE-2026-105544 in the runtime, affect all four supported lines. These are the ones most teams should treat as the main reason to patch quickly.
New Version Numbers
The updated builds to look for are:
- .NET 11.0.0, with SDK 11.0.100
- .NET 10.0.15
- .NET 9.0.23
- .NET 8.0.34
Each version has its own release notes, installers, container images, Linux packages and known issues page. Changelogs are also published for ASP.NET Core, Entity Framework Core 11.0.0 and 10.0.15, the runtime, Roslyn and Windows Forms. .NET Framework has its own November servicing notes on a separate page.
What It Means for Developers
For web teams, the large number of ASP.NET Core denial of service and privilege flaws makes this a patch to apply soon, not at the next quarterly window. Internet-facing APIs and Blazor apps are the most exposed. Rebuild self-contained apps and refresh container images, because those bundle their own runtime and will not pick up a machine-wide update.
The Visual Studio remote code execution entries matter for developer machines and build agents rather than production servers. Update Visual Studio and the SDK on every workstation and CI runner. Opening an untrusted project is a common way such bugs get triggered, so treat code from unknown sources with care.
Teams still on .NET 8 or .NET 9 should install 8.0.34 or 9.0.23 now and then plan a move. Since these are the last patches, any later flaw will stay open on those versions. .NET 10 is the long-term support choice, and the newly released .NET 11 is the short-term option with two years of support.
How to Update
Download the new SDK or runtime from the .NET download pages linked in Microsoft's post, or pull the refreshed container images. On Linux, the distribution packages carry the same fixes. After updating, confirm the installed versions with the dotnet --info command.
If a repository pins its SDK in global.json, raise the pinned version so build servers use the patched release. Then rebuild, rerun tests and redeploy. Review the known issues page for your version before rolling out widely.
Conclusion
The November 2026 .NET servicing release patches 25 CVEs, mostly in ASP.NET Core, across all supported versions. It is also the final security update for .NET 8 and .NET 9, which makes applying it and planning an upgrade equally pressing.
Sources
See my articles more often when you search Google.
