.NET 8 and .NET 9 end of support: final patches ship today
.NET 8 and .NET 9 reached end of support November 10 with final patches 8.0.34 and 9.0.23. .NET 11 shipped the same day. Retarget to net10.0 now.
Today is the last day Microsoft patches .NET 8 and .NET 9. Both versions reached end of support on November 10, 2026, and each got one final security patch on the way out: 8.0.34 and 9.0.23. After today, any new .NET 8 or 9 vulnerability stays open forever. If your store backend, booking API or internal tool runs on either one, this is your migration week.
What actually happened
- .NET 8 is an LTS release from November 2023, with 36 months of support. That window closed today.
- .NET 9 is an STS release. Microsoft stretched STS support from 18 to 24 months, which put .NET 9's end on the same day.
- After today: apps keep running, but there are no security fixes and no technical support.
- Visual Studio: a future Visual Studio 2022 update marks the .NET 8 and 9 components as out of support. There is a "remove out of support components" option to clean them up.
- The fix: change
<TargetFramework>tonet10.0, then update your build and hosting environments.
The .NET download pages confirm the final patches. Runtime 8.0.34 and 9.0.23 are both marked as security patches dated November 10, and both pages now say the release has reached end of life. The same page lists .NET 11.0.0 as released today, an STS release. It also shows .NET 10 at 10.0.15. Both .NET 10 and .NET 11 are listed with end of support on November 14, 2028.
Why .NET 8 end of support matters for your business
Install the final patch first. Get to 8.0.34 or 9.0.23 today. It does not buy you time. It closes the last holes Microsoft will ever close on those versions. Then plan the move.
Pick a target on purpose. .NET 10 and .NET 11 have the same end date right now. .NET 10 has a year of fixes behind it. .NET 11 has new features and zero field time. For a small team that wants boring, retarget to net10.0 and test. Either way, you will do this again before November 2028, so put it on the calendar now.
Ask your vendors. Microsoft's own advice for third-party .NET apps: ask the vendor for a .NET 10 build. If they have no date, that tells you how they handle security.
Check the hidden copies. Self-contained deployments and Docker images carry their own runtime. A server update does not touch them. Rebuild them.
Key takeaways
- .NET 8 and .NET 9 reached end of support on November 10, 2026
- Final security patches: runtime 8.0.34 and 9.0.23; install them today
- .NET 11.0.0 shipped the same day; .NET 10 and 11 both end November 14, 2028
- Retarget with
net10.0and rebuild self-contained apps and containers - Ask every vendor whose app runs on .NET 8 or 9 for a .NET 10 date
Runtime upgrades should be a sprint, not a crisis. We audit what your apps actually run on, retarget them, and set up CI so the next upgrade is a pull request. Book a stack review.
Sources: Microsoft .NET Blog: .NET 8 and .NET 9 end of support, .NET downloads, .NET 8.0 downloads, .NET 9.0 downloads.
- #dotnet
- #end-of-support
- #dotnet-10
- #dotnet-11
- #patch-tuesday
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
Xen Orchestra auth bypass exploited: update to 6.9.2 or 6.10.1
Xen Orchestra VSA-2026-062 lets an empty cookie log in as admin, and it's exploited. Update to 6.9.2 or 6.10.1, check for IoCs, take XO off the internet.
Read itNovember 2026 Patch Tuesday: Outlook zero-day leaks NTLM hashes
Microsoft's November 2026 Patch Tuesday fixes 1,235 flaws and an exploited Outlook zero-day, CVE-2026-124194, that leaks NTLM hashes. What to patch first.
Read it