Updated November 17, 2026. Support dates are from Microsoft's .NET support policy.
Short answer. Your .NET 8 app still runs, but it is no longer safe to leave it there. Microsoft ended support for .NET 8, and for .NET 9, on November 10, 2026. From that date there are no more security patches, so every vulnerability found from now on stays open in your app. Plan the move to .NET 10, the current long-term release, which Microsoft supports to November 14, 2028.
What changed on November 10, 2026
Microsoft supports long-term support (LTS) releases of .NET for three years and standard-term (STS) releases for two. .NET 8 was an LTS release from November 2023, so its three years ran out this month. .NET 9 ended on the same day.
| Version | Status | End of support |
|---|---|---|
| .NET 6 | Out of support | November 12, 2024 |
| .NET 7 | Out of support | May 14, 2024 |
| .NET 8 | Out of support | November 10, 2026 |
| .NET 9 | Out of support | November 10, 2026 |
| .NET 10 (LTS) | Supported | November 14, 2028 |
| .NET 11 (STS) | Supported | November 14, 2028 |
Microsoft's own wording is direct: using out-of-support .NET versions "may put your applications, application data, and computing environment at risk", and it recommends not using out-of-support software.
What "out of support" means in practice
- No security fixes. When a vulnerability is found in the .NET runtime or ASP.NET Core, the fix ships for supported versions only. Your .NET 8 app keeps the hole.
- Security reviews get harder. Customer security questionnaires, audits and cyber insurance forms often ask whether you run supported software. "No" becomes a finding you have to explain.
- Packages move on. Library authors follow Microsoft's dates and, over time, stop testing and shipping for versions Microsoft no longer supports. Each update you skip makes the eventual upgrade bigger.
- Nothing breaks on the day. The app does not stop working, which is exactly why it is easy to leave. The risk grows quietly with every month and every new vulnerability.
How risky is it to keep running .NET 8 for now?
It depends on what the app does and who can reach it.
| Your app | Risk of staying on .NET 8 | What to do |
|---|---|---|
| Public website, customer portal or API on the internet | High | Upgrade first; it is the most exposed |
| Handles payments, health or personal data | High | Upgrade first; compliance reviews will ask |
| Internal tool behind a VPN, used by staff | Medium | Schedule the upgrade in the next few months |
| Batch job or service with no outside access | Lower | Upgrade with your next planned change |
Why .NET 10, and not .NET 11
.NET 10 is the long-term release Microsoft supports to November 14, 2028. .NET 11 is a standard-term release that, under Microsoft's current policy, ends on the same day. For a business app you upgrade every few years, .NET 10 is the sensible target. Choose .NET 11 only if your team is set up to upgrade every year.
How big is the move from .NET 8 to .NET 10?
For most apps it is one of the smaller .NET upgrades, much smaller than moving off .NET Framework. The work usually is:
- Change the target framework of each project to .NET 10.
- Update NuGet packages to versions that support .NET 10, and replace any that never will.
- Check Microsoft's list of breaking changes for the areas your app uses.
- Update the SDK and runtime in your build pipeline, containers and hosting.
- Run your tests, then the old and new versions side by side on the same inputs before you switch traffic.
What makes it longer: old packages with no new version, few or no automated tests, many projects in one solution, and hosting that is pinned to a .NET 8 image or runtime.
If you are on something older
Apps on .NET 6 or .NET 7 have had no patches since 2024 and should move straight to .NET 10. Apps on .NET Framework 4.x are a different job: Web Forms pages and WCF services do not port as they are, so they are rebuilt in stages while the app stays live. Our .NET development page covers both routes.
A five-step plan for this month
- List every app and service, and the .NET version each one runs.
- Rank them by exposure, using the risk table above.
- Run a code review on the top one to size the upgrade.
- Upgrade, test side by side, and release with a rollback ready.
- Put .NET 10's end date, November 14, 2028, in your plan now, so the next move is not a surprise.
Frequently asked questions
Does .NET 8 stop working after November 10, 2026?
No. Apps on .NET 8 keep running. What stops is Microsoft's support: no more security fixes, bug fixes or technical help for .NET 8, so any vulnerability found from now on stays open in your app.
Was .NET 8 a long-term support release?
Yes. .NET 8 was an LTS release, and Microsoft supports LTS releases for three years. That three-year window closed on November 10, 2026.
Should we upgrade to .NET 10 or .NET 11?
.NET 10 for most apps. It is the current long-term support release, supported to November 14, 2028. .NET 11 is a standard-term release with the same end date, so it only makes sense if you plan to upgrade every year.
How long does a .NET 8 to .NET 10 upgrade take?
For most apps it is one of the smaller .NET upgrades: change the target framework, update packages, fix what Microsoft's breaking-change list flags for your app, and test. The real time depends on your packages, your tests and how many projects the solution has, which a code review tells you before you commit.
Is .NET 9 in the same position?
Yes. .NET 9 support also ended on November 10, 2026, so apps on .NET 9 should plan the same move to .NET 10.
Need a hand? We upgrade .NET apps for businesses in the US, UK, Canada and Australia, starting with a code review and a fixed quote. See our .NET development services or book a .NET code review.