Runtime & Platform

November 2026 Servicing Updates Released for .NET and .NET Framework

Microsoft has issued the November 2026 servicing updates for .NET 10, .NET 9, .NET 8, and .NET 11, introducing crucial security and non-security fixes. The update covers several CVEs ranging from denial of service to remote code execution across the runtime, ASP.NET Core, and Visual Studio tooling.

What changed From the source

The November 10, 2026 servicing updates deliver security and non-security fixes spanning .NET 8, .NET 9, .NET 10, and .NET 11, alongside associated tooling. The updates address numerous common vulnerabilities and exposures (CVEs) involving ASP.NET Core, .NET runtimes, and Visual Studio components.

Specific component release versions included in this rollout are runtime versions 11.0.0, 10.0.15, 9.0.23, and 8.0.34. Additional updates cover Entity Framework Core 11.0.0 and 10.0.15, Roslyn for .NET 11, SDK version 11.0.100, Windows Forms 11.0.0, and ASP.NET Core 11.0.0.

Certain vulnerabilities require specific remediation steps beyond a standard runtime update. For instance, addressing CVE-2026-118747 requires updating the System.Formats.Cbor NuGet package to version 9.0.24 for the .NET 9 package line, followed by rebuilding and redeploying applications. Similarly, CVE-2026-118741 affects ASP.NET Core Identity scaffolding and templates, requiring updates to the affected scaffolding or SDK templates alongside code correction, rebuilding, and redeployment.

  • CVE-2026-114146, CVE-2026-109475, CVE-2026-114147, and CVE-2026-105544 affect versions 8, 9, 10, and 11.
  • CVE-2026-114150 and CVE-2026-109481 affect version 11.
  • CVE-2026-109478 affects version 8.
  • New release versions include Runtime 11.0.0, 10.0.15, 9.0.23, and 8.0.34.

At a glance · Runtime & Platform

What changedWhy it mattersWho should careUpgrade and migration considerations

Why it matters Analysis

Monthly servicing updates are vital for maintaining application security and stability, directly patching vulnerabilities related to elevation of privilege, denial of service, information disclosure, and remote code execution.

The requirement to update specific NuGet packages or templates—rather than solely relying on base runtime installers—highlights the complexity of modern dependency trees. Developers must pay close attention to advisories to ensure that fixes are properly applied at both the package and code generation layers.

  • Addresses critical attack vectors across multiple active .NET versions.
  • Prevents incomplete remediation by emphasizing package and template level fixes where runtime installation alone is insufficient.

Who should care Analysis

All development teams, systems administrators, and DevOps engineers maintaining applications on .NET 8, .NET 9, .NET 10, or .NET 11 should review these advisories.

Teams utilizing Visual Studio tooling, ASP.NET Core identity templates, or specific serialization packages like System.Formats.Cbor are directly impacted and must verify their dependency configurations.

  • .NET developers working with ASP.NET Core and Identity scaffolding.
  • Enterprise IT and security teams responsible for vulnerability remediation.
  • Build and release engineers managing container images, Linux packages, and SDK deployments.

Upgrade and migration considerations Analysis

When applying the November 2026 updates, teams should verify their target frameworks and consult the individual release notes and security advisories for .NET 11, .NET 10, .NET 9, and .NET 8.

Special attention must be given to vulnerabilities like CVE-2026-118747, where installing runtime 9.0.23 alone fails to resolve the issue without updating the System.Formats.Cbor package to version 9.0.24. Affected applications utilizing vulnerable templates must also be regenerated or manually corrected, rebuilt, and redeployed.

  • Check version-specific CVE lists for precise impacts on your environment.
  • Ensure NuGet packages and SDK templates are updated alongside base runtimes.
  • Test rebuilt applications thoroughly prior to production deployment.

Sources and further reading

Original: “.NET and .NET Framework November 2026 servicing updates”, .NET Blog, published 10 Nov 2026, retrieved 10 Nov 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.