Microsoft .NET 5
Microsoft .NET 5
The Microsoft .NET 5 reached end of service life on May 10, 2022. Third-party maintenance keeps it supported — 24/7 engineering support and same-day replacement parts — at 40-70% below OEM renewal pricing.
Specifications
- product
- dotnet
- release
- 5
- product Label
- Microsoft .NET
- release Label
- 5
- codename
- lts
- latest Version
- 5.0.17
- release Date
- 2020-11-10
- maintained
- source Url
- https://endoflife.date/dotnet
Lifecycle Dates
- End of Service Life
- May 10, 2022
- Last OEM Support
- May 10, 2022
OEM vs. 3rd Party Support
See how 3rd party maintenance compares to traditional OEM support for your Microsoft .NET 5. Get the same level of service at a fraction of the cost.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| 24/7/365 Support | ||
| Same-Day Parts Replacement | Limited | |
| Mixed-Vendor Support | ||
| Flexible Contract Terms | Annual Only | Month-to-Month Available |
| Asset Lifecycle Extension | ||
| OEM-Trained Engineers |
Why Choose 3rd Party Support for Microsoft .NET 5?
Save 40-70%
Dramatically reduce your maintenance costs while maintaining the same level of support coverage.
Extend Asset Life
Continue using your Microsoft .NET 5 well beyond the OEM end-of-life date.
24/7 Expert Support
OEM-trained engineers available around the clock with same-day parts replacement.
Microsoft .NET 5 Support: Frequently Asked Questions
Is the Microsoft .NET 5 still supported?
Microsoft ended support for the Microsoft .NET 5 on May 10, 2022. Third-party maintenance remains available and keeps the Microsoft .NET 5 supported with 24/7 engineering support and same-day replacement parts.
When is the Microsoft .NET 5 end of service life (EOSL) date?
Microsoft lists the end of service life for the Microsoft .NET 5 as May 10, 2022.
Can I keep using the Microsoft .NET 5 after its EOSL date?
Yes. EOSL means Microsoft stops selling support contracts and issuing updates — the equipment itself keeps working. Third-party maintenance provides engineering support and replacement parts for as long as you choose to run it.
How much does third-party support for the Microsoft .NET 5 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Microsoft .NET 5
16 published CVEs affect the Microsoft .NET 5, including 10 rated critical or high severity. Microsoft no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2021-26701 | HIGH | 8.1 | Feb 25, 2021 | .NET Core Remote Code Execution Vulnerability |
| CVE-2021-24112 | HIGH | 8.1 | Feb 25, 2021 | .NET Core Remote Code Execution Vulnerability |
| CVE-2022-29145 | HIGH | 7.5 | May 10, 2022 | .NET and Visual Studio Denial of Service Vulnerability |
| CVE-2022-29117 | HIGH | 7.5 | May 10, 2022 | .NET and Visual Studio Denial of Service Vulnerability |
| CVE-2022-23267 | HIGH | 7.5 | May 10, 2022 | .NET and Visual Studio Denial of Service Vulnerability |
| CVE-2022-24464 | HIGH | 7.5 | Mar 9, 2022 | .NET and Visual Studio Denial of Service Vulnerability |
| CVE-2022-21986 | HIGH | 7.5 | Feb 9, 2022 | .NET Denial of Service Vulnerability |
| CVE-2021-26423 | HIGH | 7.5 | Aug 12, 2021 | .NET Core and Visual Studio Denial of Service Vulnerability |
| CVE-2020-1108 | HIGH | 7.5 | May 21, 2020 | A denial of service vulnerability exists when .NET Core or .NET Framework improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET Core or .NET Framework web application. The vulnerability can be exploited remotely, without authentication. A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the .NET Core or .NET Framework application. The update addresses the v |
| CVE-2021-31204 | HIGH | 7.3 | May 11, 2021 | .NET and Visual Studio Elevation of Privilege Vulnerability |
| CVE-2021-1721 | MEDIUM | 6.5 | Feb 25, 2021 | .NET Core and Visual Studio Denial of Service Vulnerability |
| CVE-2022-24512 | MEDIUM | 6.3 | Mar 9, 2022 | .NET and Visual Studio Remote Code Execution Vulnerability |
| CVE-2021-31957 | MEDIUM | 5.9 | Jun 8, 2021 | ASP.NET Core Denial of Service Vulnerability |
| CVE-2021-41355 | MEDIUM | 5.7 | Oct 13, 2021 | .NET Core and Visual Studio Information Disclosure Vulnerability |
| CVE-2020-8927 | MEDIUM | 5.3 | Sep 15, 2020 | A buffer overflow exists in the Brotli library versions prior to 1.0.8 where an attacker controlling the input length of a "one-shot" decompression request to a script can trigger a crash, which happens when copying over chunks of data larger than 2 GiB. It is recommended to update your Brotli library to 1.0.8 or later. If one cannot update, we recommend to use the "streaming" API as opposed to the "one-shot" API, and impose chunk size limits. |
| CVE-2021-34485 | MEDIUM | 5.0 | Aug 12, 2021 | .NET Core and Visual Studio Information Disclosure Vulnerability |
Related Microsoft Products
All Microsoft products →Microsoft .NET Core 1.0
EOSL: Jun 27, 2019
Microsoft Exchange 2013 CU23 SU21
EOSL: Apr 11, 2023
Microsoft SQL Server 2019 'Aris/Seattle'
EOSL: Jan 8, 2030
Microsoft SQL Server 2014 'Hekaton' SP2
EOSL: Jan 14, 2020
Microsoft SQL Server 2012 'Denali' SP1
EOSL: Jul 14, 2015
Microsoft .NET Core 3.1 (LTS)
EOSL: Dec 13, 2022