OSSeva Blog
SecurityNovember 2026 Patch Tuesday: the last .NET 8 and .NET 9 updates
Microsoft's 10 November 2026 Patch Tuesday was the last release for .NET 8 and .NET 9, and both reached end of support that day. It shipped .NET 8.0.34 and 9.0.23, fixing 16 CVEs in .NET 8 and 14 in .NET 9. .NET 10 received 10.0.15, and .NET 11 reached general availability the same day. From 11 November, only .NET 10 and .NET 11 get Microsoft fixes.
Running .NET in production? OSSeva patches and supports it, end-of-life versions included.
.NET extended support: what is coveredWhat shipped on 10 November 2026
The final .NET 8 and .NET 9 releases are 8.0.34 and 9.0.23, both published on 10 November 2026.
| Version | Release | Runtime | SDK | CVEs fixed | Support status after 10 Nov |
|---|---|---|---|---|---|
| .NET 8 (LTS) | 8.0.34, 10 Nov 2026 | 8.0.34 | 8.0.428 | 16 | Out of support |
| .NET 9 (STS) | 9.0.23, 10 Nov 2026 | 9.0.23 | 9.0.321 | 14 | Out of support |
| .NET 10 (LTS) | 10.0.15, 10 Nov 2026 | 10.0.15 | 10.0.404 | 16 | Supported until 14 Nov 2028 |
| .NET 11 (STS) | 11.0.0, 10 Nov 2026 | 11.0.0 | 11.0.100 | 22 | Supported until 14 Nov 2028 |
Source: Microsoft's release metadata (releases.json for 8.0, 9.0, 10.0 and 11.0) and the .NET support policy, read on 11 November 2026; Microsoft last updated the policy page on 10 November 2026. The release before this one, on 25 October 2026, shipped 8.0.33 and 9.0.22 with three CVEs each and 10.0.14 with four.
The CVEs in the final .NET 8 and 9 releases
The final .NET 8 and .NET 9 releases fixed 16 distinct CVEs: 1 rated Critical and 14 rated High by Microsoft, plus 1 Medium. 14 of them are fixed in both versions; CVE-2026-109478 and CVE-2026-118747 are fixed in .NET 8 only. Scores are CVSS v3.1 base scores from Microsoft's own CVE records, listed highest first.
| CVE | CVSS | What it affects | Fixed in |
|---|---|---|---|
| CVE-2026-114146 | 9.0 Critical | ASP.NET Core Elevation of Privilege Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-114151 | 8.8 High | Visual Studio Remote Code Execution Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-114152 | 8.8 High | Visual Studio Remote Code Execution Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-114158 | 8.8 High | Visual Studio Remote Code Execution Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-114159 | 8.8 High | Visual Studio Remote Code Execution Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-118745 | 8.8 High | Visual Studio Remote Code Execution Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-70175 | 8.1 High | ASP.NET Core Elevation of Privilege Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-105544 | 7.5 High | .NET Elevation of Privilege Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-109475 | 7.5 High | .NET Denial of Service Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-109478 | 7.5 High | ASP.NET Core Denial of Service Vulnerability | 8.0.34 only |
| CVE-2026-114147 | 7.5 High | ASP.NET Core Denial of Service Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-114149 | 7.5 High | ASP.NET Core Denial of Service Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-114154 | 7.5 High | ASP.NET Core Denial of Service Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-114157 | 7.5 High | ASP.NET Core Security Feature Bypass Vulnerability | 8.0.34 and 9.0.23 |
| CVE-2026-118747 | 7.5 High | .NET Denial of Service Vulnerability | 8.0.34 only |
| CVE-2026-109476 | 6.1 Medium | ASP.NET Core Information Disclosure Vulnerability | 8.0.34 and 9.0.23 |
Titles are Microsoft's, as published; several advisories are titled for Visual Studio but appear in the .NET 8 and .NET 9 release metadata. Microsoft's Update Guide lists each advisory with its affected product and fixed build. Check your own build numbers against it, not against this table alone.
Why 10 November was the last date
Microsoft ties .NET end-of-support dates to Patch Tuesday, the second Tuesday of the month, and its support policy lists 10 November 2026 for both .NET 8 and .NET 9. .NET 8 is a Long Term Support release with three years of support, and .NET 9 is a Standard Term Support release with two, so both windows close on the same day. The final six months of any release are the maintenance phase, in which Microsoft updates the release to fix security vulnerabilities only.
The policy also sets the bar for staying covered while a version is supported. In Microsoft's words, "Customers choosing LTS need the latest patch update installed to qualify for support." That is why the final version in the table matters: a host that stays a patch behind does not meet the policy.
What to run on 11 November
Install the final patch on every .NET 8 and .NET 9 host, then move each workload to .NET 10 or put cover in place. To see what a host runs, compare its runtimes with the final versions in the table:
dotnet --list-runtimes
dotnet --list-sdks
- Work the order in the .NET 8 end of support checklist, which starts with discovery.
- Retarget to .NET 10 with the .NET 8 to .NET 10 upgrade guide.
- Check the dates, the CVEs fixed so far and the two options on .NET 8 end of life.
- For what cannot move in time, read about extended support for .NET 8 and 9.
What did not change
Your applications still run. End of support stops Microsoft's fixes and technical support, not the runtime. Installed runtimes and NuGet packages keep working, and unsupported container tags can still be pulled, but they no longer receive updates.
The cloud platforms do not switch these apps off on the day. Azure App Service says it cannot provide security patches or related support for a runtime past its end-of-support date, and retired Azure Functions apps keep running with no security patches. AWS Lambda marks the dotnet8 runtime deprecated on 10 November 2026, blocks creating dotnet8 functions from 29 July 2027 and blocks updating them from 31 August 2027. Platform dates were checked on 28 October 2026 and are sourced in the checklist.
When the next .NET Patch Tuesday is
The next Patch Tuesday is 8 December 2026, and it covers .NET 10 and .NET 11. Microsoft says there is no guarantee that a .NET release ships on any given Patch Tuesday, so treat 8 December as the scheduled date, not a promise. OSSeva ships patched .NET 8 and 9 runtimes after 10 November 2026; Critical CVEs within 48 hours and High within 7 days.
Frequently asked questions
Is there a .NET 8 update in December 2026?
Not from Microsoft. .NET 8 reached end of support on 10 November 2026, and end of support means no further fixes or updates. The 8 December Patch Tuesday covers the versions still in support.
What is the final version of .NET 8?
The final version of .NET 8 is 8.0.34, released on 10 November 2026 with SDK 8.0.428.
Does .NET 10 still get Patch Tuesday updates?
Yes. .NET 10 is a Long Term Support release, supported by Microsoft until 14 November 2028, and it receives servicing updates on Patch Tuesday dates when Microsoft publishes them.
Tags
Related articles
.NET 8 End of Support Checklist: What to Do Now Support Has Ended
November 4, 2026Security.NET Vulnerabilities by Version: CVEs for .NET 6, 7, 8, 9 and 10
October 5, 2026Migration.NET 8 to .NET 10 Upgrade Guide: Breaking Changes, SDK Steps and a Test Plan
September 28, 2026SecurityApache Storm Vulnerabilities by Version: CVEs for Storm 1.2, 2.x and 3.x
October 6, 2026Securityetcd Vulnerabilities by Version: CVEs for etcd 3.3, 3.4, 3.5, 3.6 and 3.7
October 6, 2026SecurityClickHouse Vulnerabilities by Version: CVEs for ClickHouse 22.x to 26.x, LTS and Stable
October 6, 2026Get 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.
Prefer to talk or read more first?