Microsoft .NET 8 (LTS)
Microsoft .NET 8 (LTS)
The Microsoft .NET 8 (LTS) reached end of service life on Nov 10, 2026. Third-party maintenance keeps it supported — 24/7 engineering support and same-day replacement parts — at 40-70% below OEM renewal pricing. Coverage is available across North America, the United Kingdom and Europe, the Middle East, Asia-Pacific and Latin America, with next-business-day or 4-hour onsite response and no OEM software contract required.
- 24x7 support desk
- 4-hour onsite in major metros
- Spares held for every model we quote
- 5+ years past end of service life
- No OEM software contract required
- One contract for the whole rack
Specifications
- product
- dotnet
- release
- 8
- product Label
- Microsoft .NET
- release Label
- 8 (LTS)
- codename
- lts
- true
- latest Version
- 8.0.34
- release Date
- 2023-11-14
- maintained
- source Url
- https://endoflife.date/dotnet
Lifecycle Dates
- End of Service Life
- Nov 10, 2026
- Last OEM Support
- Nov 10, 2026
Microsoft .NET 8 (LTS) Third-Party Maintenance Pricing
Choose the response level you need. We send an indicative price within 24 hours and a firm quote within 48, typically 40-70% below the OEM renewal.
Parts and engineer onsite next business day; 24x7 phone support.
Quote this level4-hour onsite response in major metros, business hours.
Quote this levelMission-critical: 4-hour onsite response around the clock, 365 days.
Quote this levelCoverage across North America, the United Kingdom and Europe, the Middle East, Asia-Pacific and Latin America. Hardware maintenance does not require an active VMware, Broadcom or other OEM software contract.
OEM vs. 3rd Party Support
See how 3rd party maintenance compares to traditional OEM support for your Microsoft .NET 8 (LTS). 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 8 (LTS)?
Save 40-70%
Dramatically reduce your maintenance costs while maintaining the same level of support coverage.
Extend Asset Life
Continue using your Microsoft .NET 8 (LTS) 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 8 (LTS) Support: Frequently Asked Questions
Is the Microsoft .NET 8 (LTS) still supported?
Microsoft ended support for the Microsoft .NET 8 (LTS) on Nov 10, 2026. Third-party maintenance remains available and keeps the Microsoft .NET 8 (LTS) supported with 24/7 engineering support and same-day replacement parts.
When is the Microsoft .NET 8 (LTS) end of service life (EOSL) date?
Microsoft lists the end of service life for the Microsoft .NET 8 (LTS) as Nov 10, 2026.
Can I keep using the Microsoft .NET 8 (LTS) 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 8 (LTS) cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location. You get an indicative price within 24 hours and a firm quote within 48.
Known Vulnerabilities Affecting Microsoft .NET 8 (LTS)
75 published CVEs affect the Microsoft .NET 8 (LTS), including 62 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-2026-111497 | CRITICAL | 9.2 | Oct 22, 2026 | A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1 |
| CVE-2024-0057 | CRITICAL | 9.1 | Jan 9, 2024 | NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability |
| CVE-2026-71328 | HIGH | 8.8 | Sep 8, 2026 | Heap-based buffer overflow in Visual Studio allows an unauthorized attacker to execute code over a network. |
| CVE-2026-69439 | HIGH | 8.8 | Sep 8, 2026 | Heap-based buffer overflow in .NET and Visual Studio allows an unauthorized attacker to elevate privileges over a network. |
| CVE-2026-47303 | HIGH | 8.8 | Jul 14, 2026 | Authentication bypass by assumed-immutable data in ASP.NET Core allows an authorized attacker to elevate privileges over a network. |
| CVE-2026-47300 | HIGH | 8.8 | Jul 14, 2026 | Incorrect implementation of authentication algorithm in ASP.NET Core allows an authorized attacker to elevate privileges over a network. |
| CVE-2025-21176 | HIGH | 8.8 | Jan 14, 2025 | .NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability |
| CVE-2024-0056 | HIGH | 8.7 | Jan 9, 2024 | Microsoft.Data.SqlClient and System.Data.SqlClient SQL Data Provider Security Feature Bypass Vulnerability |
| CVE-2026-50528 | HIGH | 8.2 | Jul 14, 2026 | Incorrect authorization in .NET allows an unauthorized attacker to bypass a security feature over a network. |
| CVE-2026-47304 | HIGH | 8.1 | Jul 14, 2026 | Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security feature over a network. |
| CVE-2024-38229 | HIGH | 8.1 | Oct 8, 2024 | .NET and Visual Studio Remote Code Execution Vulnerability |
| CVE-2024-35264 | HIGH | 8.1 | Jul 9, 2024 | .NET and Visual Studio Remote Code Execution Vulnerability |
| CVE-2025-26646 | HIGH | 8.0 | May 13, 2025 | External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network. |
| CVE-2026-70354 | HIGH | 7.8 | Aug 11, 2026 | Out-of-bounds write in .NET allows an unauthorized attacker to execute code locally. |
| CVE-2026-62909 | HIGH | 7.8 | Aug 11, 2026 | Uncaught exception in .NET allows an authorized attacker to elevate privileges locally. |
| CVE-2026-62886 | HIGH | 7.8 | Aug 11, 2026 | Integer overflow or wraparound in .NET allows an unauthorized attacker to elevate privileges locally. |
| CVE-2026-62871 | HIGH | 7.8 | Aug 11, 2026 | Out-of-bounds write in .NET allows an unauthorized attacker to execute code locally. |
| CVE-2026-58641 | HIGH | 7.8 | Aug 11, 2026 | Integer overflow or wraparound in .NET allows an unauthorized attacker to elevate privileges locally. |
| CVE-2026-50650 | HIGH | 7.8 | Jul 14, 2026 | Improper control of generation of code ('code injection') in .NET Framework allows an unauthorized attacker to elevate privileges locally. |
| CVE-2026-50649 | HIGH | 7.8 | Jul 14, 2026 | Deserialization of untrusted data in .NET allows an unauthorized attacker to execute code locally. |
Showing the 20 most severe of 75 known CVEs.
Get Third Party SupportRelated Microsoft Products
All Microsoft products →Microsoft SQL Server 2014 'Hekaton' SP2
EOSL: Jan 14, 2020
Microsoft SQL Server 2012 'Denali'
EOSL: Jan 14, 2014
Microsoft Windows 10 1909 (E)
EOSL: May 10, 2022
Microsoft SQL Server 6.0 'SQL95' SP3
EOSL: Mar 31, 1999
Microsoft SQL Server 2008 'Katmai' SP3
EOSL: Oct 13, 2015
Microsoft SQL Server 2019 'Aris/Seattle'
EOSL: Jan 8, 2030