.NET versions
.NET: update to 11.0.0 or 10.0.15. 9 and older have reached end of life in the lifecycle data.
Data: .
Which .NET branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 1122 CVE records | Fixes until 14 November 2028 | 11.0.0 | 11.0.0 (this branch) |
| 10110 CVE records | Fixes until 14 November 2028 | 10.0.15 | 10.0.15 (this branch) |
| 9117 CVE records | Ended on 10 November 2026 | None, the branch has ended | 10.0.15 (move to 10) |
| 8135 CVE records | Ended on 10 November 2026 | None, the branch has ended | 10.0.15 (move to 10) |
| 739 CVE records | Ended on 14 May 2024 | None, the branch has ended | 10.0.15 (move to 10) |
| 649 CVE records | Ended on 12 November 2024 | None, the branch has ended | 10.0.15 (move to 10) |
| 518 CVE records | Ended on 10 May 2022 | None, the branch has ended | 10.0.15 (move to 10) |
| 3.130 CVE records | Ended on 13 December 2022 | None, the branch has ended | 10.0.15 (move to 10) |
| 3.04 CVE records | Ended on 3 March 2020 | None, the branch has ended | 10.0.15 (move to 10) |
| 2.214 CVE records | Ended on 23 December 2019 | None, the branch has ended | 10.0.15 (move to 10) |
| 2.131 CVE records | Ended on 21 August 2021 | None, the branch has ended | 10.0.15 (move to 10) |
| 2.014 CVE records | Ended on 1 October 2018 | None, the branch has ended | 10.0.15 (move to 10) |
| 1.118 CVE records | Ended on 27 June 2019 | None, the branch has ended | 10.0.15 (move to 10) |
| 1.019 CVE records | Ended on 27 June 2019 | None, the branch has ended | 10.0.15 (move to 10) |
Exploited, or likely to be
CVE records for .NET that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the release that fixes each in every branch.
| Record | Signs of exploitation | Fixed in |
|---|---|---|
| CVE-2020-1147.NET Framework, SharePoint, and Visual Studio Remote Code Execution7.8 High · published 14 July 2020 | On CISA's list Metasploit module Exploit-DB entry EPSS 0.50 or more | Fixed in 3.1.6, 2.1.20 |
| CVE-2023-44487Rapid Reset Attack7.5 High · published 10 October 2023 | On CISA's list Exploit-DB entry EPSS 0.50 or more | Fixed in 7.0.13, 7.0.12, 6.0.24, 6.0.23 |
| CVE-2026-111497Out-of-Bounds Write in Google Brotli Decoder9.2 Critical · published 22 October 2026 | On CISA's list EPSS 0.50 or more | Fixed in 10.0.14, 9.0.22, 8.0.33 |
| CVE-2023-38180.NET and Visual Studio Denial of Service Vulnerability7.5 High · published 8 August 2023 | On CISA's list | Fixed in 7.0.10, 6.0.21 |
| CVE-2025-55315ASP.NET Security Feature Bypass Vulnerability9.9 Critical · published 14 October 2025 | Exploit-DB entry EPSS 0.50 or more | Fixed in 9.0.10, 8.0.21 |
| CVE-2018-8269A denial of service vulnerability exists when OData Library improperly handles web requests, aka "OData Denial of Service Vulnerability." This affects Microsoft.Data.OData.published 13 September 2018 | Exploit-DB entry | Fixed in 2.2.7, 2.1.13 |
| CVE-2023-38171Microsoft QUIC Denial of Service Vulnerability7.5 High · published 10 October 2023 | EPSS 0.50 or more | Fixed in 7.0.13, 7.0.12 |
CISA's list for the vendor
The entries CISA lists under the vendor names it uses for .NET, each with its patch-first group.
- Microsoft: exploited vulnerabilities392 entries
More .NET pages
- .NET 10.0.43 CVE records
- .NET 8.0.03 CVE records
- .NET 3.0.24 CVE records
What this page counts
The branches and their dates are from the product lifecycle data credited under Sources. The newest release of a branch is the newest of that data and of the project's release notes.
The fixes are the CVE ids that the project's release notes list for each release: 247 CVE ids in 181 releases. A record says nothing of its own here: only a release whose notes list it fixes it. A record that Microsoft's CVE Numbering Authority published, that names .NET and that names the newest release of a branch as affected means the branch has no safe release yet.
A branch that has ended is rarely named in a new record. That is not a sign that it is safe. Not tested by the project, treat as affected.
A release gets a page of its own when it fixes three or more CVE records, or any record that CISA lists as exploited or that EPSS rates 0.50 or more, and keeps it. Any other release is a row on its branch page.
2 records that name the platform are listed by no release in the project's release notes, so no branch or release row counts them: CVE-2026-56170 and CVE-2026-70194.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Release notes of the .NET runtime from the dotnet/core repository, Copyright (c) .NET Foundation and Contributors (MIT License) (source). Licence: MIT License
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)