.NET 7 end of life
.NET 7 reached end of support on 14 May 2024. It was a standard-term support release with an 18-month life. Microsoft's final build, 7.0.20, shipped on 28 May 2024 with the fix for CVE-2024-20672, and nothing has shipped for .NET 7 since. .NET 10 is the current LTS, supported until 14 November 2028. OSSeva ships patched .NET 7 runtimes today.
- End of life
- 14 May 2024
- Released
- Nov 2022
- Final release
- 7.0.20
- Successor
- .NET 10 (LTS)
Date published by .NET and .NET Core support policy. We do not publish a lifecycle date we cannot source.
Last reviewed
What actually stops on 14 May 2024
- Security updates for the .NET 7 runtime, ASP.NET Core 7 and the 7.0 SDK. Runtime 7.0.20 and SDK 7.0.410 were the last.
- Microsoft support cases for applications on .NET 7.
- Fixes for later .NET advisories. Microsoft ships them to supported versions only.
What actually breaks in the upgrade
.NET 8 is not the destination
.NET 8 and .NET 9 both reach end of support on 10 November 2026. An application that moves from 7 to 8 now meets the same problem within weeks. .NET 10, supported until 14 November 2028, is the target that buys time.
Retargeting is the easy half
Changing the target framework from net7.0 to net10.0 is one line. The work is in NuGet dependencies that pinned 7.x packages, ASP.NET Core breaking changes across three releases, and the test suite that proves nothing moved.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to .NET 10 | Retarget, update dependencies, retest. | Weeks | Engineering time | The destination. Supported to November 2028. |
| Upgrade to .NET 8 | A smaller jump to an LTS that ends on 10 November 2026. | Days to weeks | Engineering time | Not worth it now. The deadline arrives before most projects finish. |
| OSSeva patched .NET 7 | Signed .NET 7 runtimes with backported security fixes. | Days | Subscription | For applications that cannot be retargeted before the next audit. |
| Stay unpatched | No fixes since May 2024. | None | Zero now | Hard to defend for anything that faces the internet. |
What OSSeva does for .NET 7
OSSeva patches this line
OSSeva ships patched .NET 7 runtimes now, with security fixes backported to the runtime and ASP.NET Core 7, on the Patch, Assure and Operate tiers.
.NET extended supportWhat your auditor will say
Every system component in the cardholder data environment needs its applicable security patches. A runtime or broker with no upstream fix supply needs a patched source or a documented compensating control.
Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.
.NET 7: common questions
When did .NET 7 reach end of support?
On 14 May 2024. Microsoft shipped one more security release, 7.0.20, on 28 May 2024, and nothing since.
Why was .NET 7 supported for only 18 months?
.NET 7 was a standard-term support release. Microsoft's long-term support releases, such as .NET 8 and .NET 10, run for three years.
Should I upgrade from .NET 7 to .NET 8 or .NET 10?
.NET 10. .NET 8 reaches end of support on 10 November 2026, and .NET 10 is supported until 14 November 2028.
Can I get security patches for .NET 7?
Not from Microsoft. OSSeva ships patched .NET 7 runtimes today.
Still running .NET 7?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.