· · 2 minutes read

.NET April 2026 Servicing — Security Patches You Should Apply Today

The April 2026 servicing release patches 6 CVEs across .NET 10, .NET 9, .NET 8, and .NET Framework — including two remote code execution vulnerabilities.

dotnet security servicing dotnet-framework
This post is also available in:Español, Deutsch, Français, Português, Italiano, 日本語, 中文, 한국어, Русский

The April 2026 servicing updates for .NET and .NET Framework are out, and this one includes security fixes you’ll want to apply soon. Six CVEs patched, including two remote code execution (RCE) vulnerabilities.

What’s patched

Here’s the quick summary:

CVETypeAffects
CVE-2026-26171Security Feature Bypass.NET 10, 9, 8 + .NET Framework
CVE-2026-32178Remote Code Execution.NET 10, 9, 8 + .NET Framework
CVE-2026-33116Remote Code Execution.NET 10, 9, 8
CVE-2026-32203Denial of Service.NET 10, 9, 8 + .NET Framework
CVE-2026-23666Denial of Service.NET Framework 3.0–4.8.1
CVE-2026-32226Denial of Service.NET Framework 2.0–4.8.1

The two RCE CVEs (CVE-2026-32178 and CVE-2026-33116) affect the broadest range of .NET versions and should be the priority.

Updated versions

  • .NET 10: 10.0.6
  • .NET 9: 9.0.15
  • .NET 8: 8.0.26

All are available via the usual channels — dotnet.microsoft.com, container images on MCR, and Linux package managers.

What to do

Update your projects and CI/CD pipelines to the latest patch versions. If you’re running containers, pull the latest images. If you’re on .NET Framework, check the .NET Framework release notes for the corresponding patches.

For those running .NET 10 in production (it’s the current release), 10.0.6 is a mandatory update. Same for .NET 9.0.15 and .NET 8.0.26 if you’re on those LTS tracks. Two RCE vulnerabilities are not something you postpone.

Share:
View source code for this post on GitHub ↗
← Aspire 13.2 Gets MongoDB EF Core and Azure Data Lake — Two Integrations Worth Trying
Pin Clustering Finally Lands in .NET MAUI Maps — One Property, Zero Pain →