ASP.NET 10.0.10
Microsoft has shipped ASP.NET Core 10.0.10, the latest servicing release of the web framework, as part of the .NET 10.0.10 update that rolled out on July 14, 2026. The release is a maintenance update focused on bug fixes and dependency refreshes rather than new features, with notable corrections across Blazor, OpenAPI tooling, and signal processing internals.
What Changed
Blazor developers get two fixes worth knowing about. The OwningComponentBase Dispose method in .NET 10 regains its original behavior, undoing a behavioral regression from earlier in the 10.0 line, and a null reference error in the Virtualize component has been resolved. The Identity Web packages were also refreshed to version 3.15.0.
- Blazor — OwningComponentBase.Dispose restores original .NET 10 behavior; Virtualize null reference error fixed
- OpenAPI — DescriptionAttribute now handled for nullable value types; duplicate XML documentation IDs for generic properties fixed
- Security — KeyRingProvider thread pool starvation on cold start addressed
- Dependencies — Microsoft Identity Web bumped to 3.15.0; npm and submodule dependencies updated
Why It Matters
Servicing releases like this one are the recommended update path for production workloads on .NET 10. The KeyRingProvider fix, in particular, targets a cold-start pathology where data protection key resolution could stall worker threads — the kind of issue that shows up as mysterious latency spikes after a fresh deployment. The OpenAPI corrections also matter for teams generating clients from nullable value type endpoints, where descriptions were previously dropped.
What's Next
ASP.NET Core 10.0.10 is available now through the regular channels: dotnet SDK installers, container images on mcr.microsoft.com, and package updates from NuGet. As with all .NET servicing releases, the update is compatible with existing 10.0.x applications — a straightforward dotnet --version check and package bump will get you current. The next scheduled servicing wave is expected in August.