cd /news/developer-tools/net-8-and-net-9-both-die-on-november… · home topics developer-tools article
[ARTICLE · art-61367] src=dev.to ↗ pub= topic=developer-tools verified=true sentiment=· neutral

.NET 8 and .NET 9 Both Die on November 10 - Yes, the LTS Too

Microsoft's .NET 8 and .NET 9 will both reach end of support on November 10, 2026, despite .NET 8 being an LTS release. After that date, no security patches will be issued for either runtime, creating compliance risks for organizations. The upgrade path to .NET 10 (LTS) is straightforward for most teams, but those with dependencies pinned to EOL runtimes may face challenges.

read2 min views1 publishedJul 16, 2026

Originally published at endoflife.ai.

Here's a date collision that surprises people: .NET 8 and .NET 9 reach end of support on the same day — November 10, 2026.

The instinctive reaction is "but 8 is the LTS!" — and that's exactly the trap. LTS doesn't mean long, it means longer. The math:

Different tracks, same cliff. Anyone who "played it safe" on the LTS and anyone who rode the STS end up in the identical position this November.

After November 10, Microsoft ships no security patches for either runtime — including for vulnerabilities that get actively exploited later. Your app keeps running; it just stops getting defended. CVEs published against the runtime after that date are permanent for you.

For teams with compliance obligations, "unsupported runtime in production" is an audit finding, not a philosophical debate.

.NET 10 (LTS) shipped November 11, 2025 and is supported to November 14, 2028. For most 8→10 moves the upgrade is mercifully boring — retarget, run the test suite, chase a handful of breaking changes. The teams that get hurt are the ones who discover a transitive dependency pinned to an EOL runtime in December, not the ones who retargeted in September.

Worth separating in your head: .NET Framework 4.8 (the old Windows-only one) is a different animal — it has no fixed end date and lives as long as the Windows version hosting it. Modern .NET (Core lineage) is the one on the November clock. If you're still on Framework, your deadline is your Windows Server's deadline instead.

The November 10 cutoff sits inside a brutal H2 2026 calendar: SharePoint 2016/2019 and SQL Server 2016 already died July 14, OpenSSL 3.0 goes September 7, Python 3.10 on October 31, PostgreSQL 14 on November 12, PHP 8.2 on December 31.

Every date above is verified against vendor lifecycle sources. Full deadline coverage lives at endoflife.ai/eol-watch, you can check any product's status in seconds with the EOL checker, or scan a whole project file with the stack scanner. There's also a free API if you'd rather gate this in CI:

curl https://api.endoflife.ai/v1/status/dotnet/8
── more in #developer-tools 4 stories · sorted by recency
── more on @microsoft 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/net-8-and-net-9-both…] indexed:0 read:2min 2026-07-16 ·