deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

.NET 8 and .NET 9 reach end of support on Microsoft's largest Patch Tuesday

Microsoft ended support for .NET 8 and .NET 9 on November 10, 2026 — the same day it shipped nearly 1,100 security fixes, a record Patch Tuesday. Apps keep running, but new flaws will never be patched.

.NET 8 and .NET 9 reach end of support on Microsoft's largest Patch Tuesday

What happened

On November 10, 2026, Microsoft retired two .NET versions at once. According to a dev.to post rounding up the event, .NET 8 (the long-term support release) and .NET 9 (the short-term support release) both stopped receiving security fixes and technical support that day. The overlap was a side effect of scheduling: Microsoft had stretched the support window for STS releases from 18 to 24 months, and .NET 9's arithmetic landed on the same end date as .NET 8's.

The timing had been public since June. The official recommendation is to migrate to .NET 10, an LTS release supported until November 2028. Nothing breaks immediately — applications on .NET 8 and 9 will keep running — but any vulnerability discovered from this point onward will go unfixed on those versions.

A record Patch Tuesday on the same day

What turned the end-of-support date into a larger story is that November 10 also brought what the post calls the biggest Patch Tuesday in history. According to Krebs on Security, Microsoft fixed 1,093 vulnerabilities, 63 of them critical, including one actively exploited spoofing flaw in Outlook tracked as CVE-2026-124194.

The precise number depends on who is counting. The dev.to post notes that other outlets reported 1,094, 1,095 or as many as 1,235, because each publication draws the line differently around first-party products, third-party components and cloud service flaws. The scale is what matters: a year earlier the monthly average was roughly 100 fixes, October 2026 delivered more than 1,400, and the 2026 total has already passed 5,100. The post attributes the jump, as Microsoft itself has, to the use of AI in searching for flaws.

What this means in practice

For years, framework upgrades sat at the bottom of the backlog under a tech-debt label. The post argues that this posture assumed a slow, predictable pace of vulnerability disclosure — an assumption a tenfold increase in published flaws within a year invalidates. Running an unsupported version is no longer an abstract risk; it is a visible, open window to anyone reading the bulletins.

Enterprise realities complicate the picture. Many teams do not choose their .NET version: an application may run on a server managed by another team, under a vendor contract where migration is still being evaluated. Microsoft's guidance in that scenario is to ask the vendor for an updated version. Visual Studio 2022 users should also prepare for an upcoming update that will flag .NET 8 and .NET 9 components as out of support, so checking installer settings in advance is worthwhile.

For perspective, Chris Goettl of Ivanti, cited in the post, points out that of roughly 95,000 CVEs assigned in 2026, only 217 made it onto CISA's known exploited vulnerabilities list. Most flaws never become attacks — but nobody can predict which one will be next, and that is exactly where a framework without patches hurts more than an up-to-date operating system.

The migration itself is often manageable: for most projects, changing the TargetFramework to .NET 10, running a round of tests and reviewing the breaking changes. The real effort goes into old dependencies, pipelines pinned to specific container images and hosting environments nobody has touched in two years. The post's practical suggestion is to start with an inventory — a simple spreadsheet listing service name, version and owner already solves half the problem.

Why it matters

This story fuses two trends into a single operational problem. Vulnerability discovery is accelerating — Microsoft itself links the record numbers to AI-assisted searching — while support windows remain fixed in time. That combination shortens the gap between a flaw being known and a flaw being exploited, which turns staying on a maintained runtime into a security decision rather than routine housekeeping. For any organisation still running .NET 8 or .NET 9 in production, the clock started on November 10: every future bulletin is now a list of weaknesses those versions will never be patched against.

  • #dotnet
  • #microsoft
  • #security
  • #patch-management
  • #end-of-support

Related posts