Back to blog

OSSeva Blog

Security

.NET 8 Extended Support After 10 November 2026: Who Patches It Now

Randall McClureUpdated 11 min read

The short answer

Microsoft ended support for .NET 8 and .NET 9 on 10 November 2026, with 8.0.34 and 9.0.23 as the final patches; .NET 10 (10.0.15) is supported to 14 November 2028. To stay on 8 or 9, you need a third-party provider. Microsoft sells no extension, and after that date three vendors sell patched .NET builds: HeroDevs (Never-Ending Support for .NET 6, 8 and 9), TuxCare (Endless Lifecycle Support for .NET 6, 8 and 10, which does not list 9) and OSSeva (patched .NET 6 and 7 runtimes, and .NET 8 and 9 from 10 November 2026). Canonical maintains the .NET 8 packages in the built-in Ubuntu 22.04 and 24.04 feed for the life of those releases, which Microsoft Learn states in its Ubuntu guide.

Comparing HeroDevs with the other options? HeroDevs alternatives for end-of-life open source lists its .NET, Spring and PostgreSQL versions next to what OSSeva patches.

The supported route from Microsoft is .NET 10, an LTS release. Buying time from a provider is for the applications that did not get there by 10 November. The dates are on the .NET 8 end of life dates and CVEs and .NET 9 pages, and what OSSeva covers is on the .NET 8 and .NET 9 extended support from OSSeva page. If your .NET 8 estate is still open, start with the .NET 8 end of support checklist.

Running .NET in production? OSSeva patches and supports it, end-of-life versions included.

.NET extended support: what is covered

.NET support dates

VersionTypeReleasedMicrosoft support ends
.NET 6LTS8 November 202112 November 2024
.NET 7STS8 November 202214 May 2024
.NET 8LTS14 November 202310 November 2026
.NET 9STS12 November 202410 November 2026
.NET 10LTS11 November 202514 November 2028
.NET 11STS10 November 202614 November 2028

LTS releases get three years of free support and STS releases two, which is why .NET 8 and .NET 9 ended on the same Patch Tuesday. The .NET end-of-life chart tracks every line, and .NET vulnerabilities by version shows which advisories already reach the older ones.

How third-party .NET 8 support compares with Microsoft's policy

Microsoft's policy gives LTS releases three years of support and requires the latest patch to qualify; after the end date it ships nothing more for .NET 8 or 9. A provider replaces that with its own patch window and scope, so the question to ask is what each one states.

Source.NET versions covered after 10 Nov 2026Stated patch window
Microsoft support policyNone for .NET 8 or 9 (final releases 8.0.34 and 9.0.23); .NET 10 to 14 November 2028LTS: three years of free patches, latest patch required to qualify
OSSeva Patch.NET 6 to 9, and .NET 10 after 14 November 2028Critical (CVSS 9.0+) within 48 hours; High within 7 days (OSSeva support SLA)
HeroDevs NES.NET 6, 8 and 9Its .NET page says response times vary by severity, with security issues "resolved immediately (same day if possible)", and offers the SLA on request. Its SLA documentation sets targets of 14 days for Critical and 30 days for High
TuxCare ELS.NET 6, 8 and 10 (.NET 9 is not listed)14 days from public disclosure for critical and high severity (CVSS 7.0+), 60 days for medium, 90 days for low

Microsoft's figures are from its .NET support policy page, HeroDevs' from herodevs.com/support/dot-net-nes and docs.herodevs.com/sla, and TuxCare's from tuxcare.com/endless-lifecycle-support/net-eol-support, all read on 14 November 2026. HeroDevs calls its figures targets. For OSSeva's own coverage, see .NET 8 and .NET 9 extended support from OSSeva.

.NET 8 patch providers compared

Each row reflects what the vendor publishes on its own site: Microsoft, HeroDevs and TuxCare as of 14 November 2026, Canonical as of 6 October 2026.

ProviderBest forWhat it coversVersionsDelivery modelSelf-managed?
MicrosoftAnyone who can be on .NET 10Free patches until the end-of-support date. No paid extension for .NET.NET 8 and 9 ended 10 November 2026; .NET 10 to 14 November 2028Microsoft builds, packages and container imagesYes
HeroDevs Never-Ending SupportTeams on .NET 8 and 9 that also have other end-of-life frameworks, such as Angular or SpringA drop-in replacement for the unsupported runtime, with CVE fixes aligned to Microsoft's Patch Tuesday; its page also lists Entity Framework, WPF and WinForms.NET 6, 8 and 9Packages through repository managers such as Nexus and Artifactory; Windows and LinuxYes
TuxCare Endless Lifecycle SupportWindows-heavy estates (IIS) on .NET 8, or teams that already buy TuxCare for Linux or other runtimesSecurity patches for the .NET runtime, ASP.NET Core runtime, SDK and Desktop runtime, with a published 14, 60 and 90 day window by severity.NET 6, 8 and 10Linux, and Windows from Server 2012 to 2025, Windows 10 22H2 and Windows 11, on x64 and x86Yes
OSSevaContainerised .NET services, or estates that want patches, 24/7 operations and a migration assessment from one teamQuarterly CVE patches covering the CLR, ASP.NET Core, Entity Framework Core and the base class libraries; migration assessment and 24/7 operations on higher tiers.NET 6 and 7, and .NET 8 and 9 from 10 November 2026Signed (GPG and Sigstore) Docker images for SDK and ASP.NET Core runtime, apt and yum packages, binaries on Linux; installers on WindowsYes
Canonical (Ubuntu)Applications that install .NET 8 from Ubuntu's own packagesMaintains the .NET packages in Ubuntu's built-in feed for the lifetime of that Ubuntu release, beyond Microsoft's date (Microsoft Learn, read 17 November 2026).NET 8 on Ubuntu 22.04 LTS and 24.04 LTSAPT packages from the Ubuntu archiveYes, on Ubuntu

Two limits are easy to miss. Canonical's commitment covers .NET installed from Ubuntu's built-in feed; Microsoft Learn (read 17 November 2026) says the backports feed, where .NET 9 sits on Ubuntu 24.04, is best effort and does not extend beyond Microsoft's support lifetime, and .NET pulled from Microsoft's images or the install script is outside it. And none of the version lists above includes the Windows-only .NET Framework 4.x, which follows its own Windows lifecycle.

How the providers differ

HeroDevs

HeroDevs announced NES for .NET 8 in April 2026, on both Windows and Linux. It also covers .NET 9, which suits teams that moved to the STS release early and now share .NET 8's lapsed deadline. Its .NET page lists .NET 6, 8 and 9, is priced as "Custom Pricing" billed annually, and also names Entity Framework, WPF and WinForms. See HeroDevs alternative compared.

TuxCare

TuxCare publishes the most detailed Windows matrix of the group, from Windows Server 2012 to 2025 on x64 and x86, which matters for IIS-hosted applications. Its list covers .NET 6, 8 and 10 but not 7 or 9, so a .NET 9 service needs another provider or a move to 10. TuxCare also publishes the clearest patch window of the three, 14 days for CVSS 7.0 and above. See OSSeva vs TuxCare.

OSSeva

OSSeva for .NET patches .NET 6 and 7, and since 10 November 2026 .NET 8 and 9 as well, covering LTS and STS releases alike. Fixes reach the CLR, ASP.NET Core, Entity Framework Core and the base class libraries, delivered as drop-in Docker base images for the SDK and the ASP.NET Core runtime in Alpine and Debian variants, so a container moves by changing its FROM line. Windows hosts get patched builds as installers. Assure adds NuGet dependency scanning, ASP.NET Core TLS and authentication review, SOC 2 and HIPAA attestation material and a migration assessment; Operate adds 24/7 monitoring and runs the version migration. OSSeva's patched builds are for .NET (Core and 5 and later); .NET Framework 4.x is not part of them.

Canonical

Ubuntu has published .NET in its own archive since 22.04, and .NET 8 sits in the main repository of both 22.04 and 24.04. Microsoft Learn's Ubuntu guide (updated 11 November 2026) states that Canonical supports .NET versions in the built-in Ubuntu feed for the lifetime of that Ubuntu version, even beyond Microsoft's support lifetime, and lists .NET 8 in the built-in feed of both releases. If your applications install .NET 8 from Ubuntu's packages, this may already cover you. It does not help applications on Windows, on other distributions, or on Microsoft's container images.

How we chose the providers

We read each vendor's own .NET page and its published SLA or pricing page on 14 November 2026, and Microsoft's .NET support policy and .NET Framework lifecycle FAQ the same day. Microsoft's Ubuntu guide and the TuxCare docs page were read on 17 November 2026, when TuxCare's docs page listed Windows only; its product page lists Linux and Windows. OSSeva is one of the options compared, and the rows are not a ranking. We compared what providers publish; we did not run their builds or audit their claims, and a provider not listed is one we did not verify.

Migration options for apps on unsupported .NET

Most apps should move to .NET 10 LTS; the usual blockers are a dependency with no .NET 10 release, a validation cycle that must re-run, or an application due for retirement. The move from .NET 8 to .NET 10 is one LTS step, and for most code it is a retarget, a dependency refresh and a test cycle. Extended support earns its cost where something outside the code sets the pace:

SituationUsual answer
Application under active development, dependencies already support .NET 10Migrate now; the 10 November date has passed
Third-party packages or vendor SDKs have no .NET 10 release yetExtended support until the slowest dependency catches up
Validated or certified releases, common in healthcare and financeExtended support while the assurance process re-runs on .NET 10
Stable internal service due for retirement within a year or twoExtended support until retirement
Estate on .NET 6 or 7Already out of support; patch now, then plan the jump to .NET 10
Legacy .NET Framework 4.x applicationA separate decision: Framework follows the Windows lifecycle, and a move to modern .NET is a port, not an upgrade

Whichever way an application goes, record its target date. Buying support for an application with no migration date tends to turn a bridge into a permanent cost. Our .NET 8 to .NET 10 upgrade guide lists the breaking changes, SDK steps and a test plan.

Does Microsoft offer extended security updates for .NET Framework?

Not as a separate .NET Framework program. Microsoft's .NET Framework lifecycle FAQ (read 14 November 2026) says .NET Framework 4.5.2 and later is a component of Windows and gets the same support as the Windows version it is installed on, so its end date comes from the operating system, not from .NET. That is also why none of the third-party lists above includes it, and why OSSeva's patched builds cover .NET (Core and 5 and later), not .NET Framework.

Where OSSeva fits

OSSeva keeps .NET 6 to 9 patched past Microsoft's dates with signed runtime builds and container images, and can run the applications 24/7 while they move. See .NET 8 and .NET 9 extended support from OSSeva for the offer, and the extended support vendor roundup for how OSSeva compares by technology layer. It is not the right fit if you can upgrade to .NET 10 this quarter (do that), if the application is .NET Framework 4.x, or if the exposure is mostly front-end frameworks, where HeroDevs alternative compared explains where HeroDevs is the stronger choice.

Frequently asked questions

Is .NET 8 still supported?

No. Microsoft support for .NET 8 ended on 10 November 2026. The app keeps running, but runtime fixes now come only from a third-party provider.

What was the last .NET 8 patch?

8.0.34, released on 10 November 2026. The last .NET 9 release was 9.0.23, and .NET 10 was at 10.0.15 the same day.

Who provides extended support for .NET 8 after November 2026?

HeroDevs (Never-Ending Support for .NET 6, 8 and 9), TuxCare (Endless Lifecycle Support for .NET 6, 8 and 10), OSSeva (.NET 8 and 9 from 10 November 2026, alongside .NET 6 and 7) and Canonical, which maintains the .NET 8 packages in the Ubuntu 22.04 and 24.04 built-in feed for the life of those releases. Microsoft itself offers no extension.

Does Microsoft sell extended support for .NET 8?

No. Microsoft's .NET support policy gives LTS releases three years of free support and lists no paid extension. Once support ends, the policy recommends accelerating plans to stop using that version.

What are the best options for .NET 8 applications that need CVE coverage past end of support?

Move to .NET 10 where you can. For applications that cannot move yet, use third-party extended support from HeroDevs, TuxCare or OSSeva, or Ubuntu's own .NET 8 packages if the application runs on Ubuntu 22.04 or 24.04. Pick by platform: all three vendors cover Linux and Windows. OSSeva delivers Windows installers and Linux packages, Docker images and binaries.

Should we migrate from legacy .NET or buy extended support?

Migrate applications that are still changing and whose dependencies are ready. Buy support for those blocked by dependencies, validation cycles or planned retirement, with a migration date recorded for each. For .NET Framework 4.x, the question is a port to modern .NET rather than an upgrade.

Do .NET 8 applications stop working after 10 November 2026?

No. They keep running. They stop receiving Microsoft security fixes, so runtime vulnerabilities published after that date stay open unless a provider patches them.

Does extended support cover .NET 9 as well?

HeroDevs and OSSeva cover .NET 9. TuxCare's published list skips it, and Ubuntu 24.04 ships .NET 9 only through a backports archive that is not maintained past Microsoft's date.

Tags

.NETEnd of LifeExtended SupportVendor ComparisonPatching

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call