← Search results
CVE-LINKED INVENTORY17 SECURITY RECORDS
Microsoft
.NET 8.0
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-62871 | 11 Aug 2026 | .NET 8.0: 8.0.0 < 8.0.30; .NET 9.0: 9.0.0 < 9.0.19; Microsoft Visual Studio 2022 version 17.14: 17.14.0 < 17.14.38; Microsoft Visual Studio 2026 version 18.8: 18.0 < 18.8.3 | 8.0.30:Security Update:https://support.microsoft.com/help/5122104 | Update reference ↗ |
| CVE-2026-62902 | 11 Aug 2026 | .NET 8.0: 8.0.0 < 8.0.30; .NET 9.0: 9.0.0 < 9.0.19; Microsoft Visual Studio 2022 version 17.14: 17.14.0 < 17.14.38; Microsoft Visual Studio 2026 version 18.8: 18.0 < 18.8.3 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-50650 | 14 Jul 2026 | .NET 8.0: 8.0.0 < 8.0.29; .NET 9.0: 9.0.0 < 9.0.18; Microsoft .NET Framework 3.5: 3.5.0 < 2.0.50727.8983 & 3.0.30729.8978; Microsoft .NET Framework 3.5 AND 4.7.2: 4.7.0 < 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0; Microsoft .NET Framework 3.5 AND 4.8: 4.8.0 < 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0; Microsoft .NET Framework 3.5 AND 4.8.1: 4.8.1 < 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0; Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2: 4.7.0 < 4.7.4143.0; Microsoft .NET Framework 4.8: 4.8.0 < 4.8.4803.0; Microsoft Visual Studio 2022 version 17.12: 17.12.0 < 17.12.22; Microsoft Visual Studio 2022 version 17.14: 17.14.0 < 17.14.36; Microsoft Visual Studio 2026 version 18.7: 18.0 < 18.7.4 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-50649 | 14 Jul 2026 | .NET 8.0: 8.0.0 < 8.0.29; .NET 9.0: 9.0.0 < 9.0.18; Microsoft .NET Framework 3.5: 3.5.0 < 2.0.50727.9182 & 3.0.30729.9168; Microsoft .NET Framework 3.5 AND 4.7.2: 4.7.0 < 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0; Microsoft .NET Framework 3.5 AND 4.8: 4.8.0 < 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0; Microsoft .NET Framework 3.5 AND 4.8.1: 4.8.1 < 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0; Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2: 4.7.0 < 4.7.4143.0; Microsoft .NET Framework 4.8: 4.8.0 < 4.8.4803.0; Microsoft .NET Framework 4.8.1: 4.8.0.0 < 4.8.9340.0; Microsoft Visual Studio 2026 version 18.7: 18.0 < 18.7.4 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-50646 | 14 Jul 2026 | .NET 8.0: 8.0.0 < 8.0.29; .NET 9.0: 9.0.0 < 9.0.18; Microsoft .NET Framework 3.5: 3.5.0 < 2.0.50727.8983 & 3.0.30729.8978; Microsoft .NET Framework 3.5 AND 4.7.2: 4.7.0 < 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0; Microsoft .NET Framework 3.5 AND 4.8: 4.8.0 < 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0; Microsoft .NET Framework 3.5 AND 4.8.1: 4.8.1 < 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0; Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2: 4.7.0 < 4.7.4143.0; Microsoft .NET Framework 4.8: 4.8.0 < 4.8.4803.0; Microsoft Visual Studio 2022 version 17.12: 17.12.0 < 17.12.22; Microsoft Visual Studio 2022 version 17.14: 17.14.0 < 17.14.36; Microsoft Visual Studio 2026 version 18.7: 18.0 < 18.7.4 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-55248 | 14 Oct 2025 | 8.0.0 < 8.0.21; 9.0.0 < 9.0.10; 2.0.0 < 2.0.50727.8981; 3.0.0 < 2.0.50727.8981; 3.5.0 < 2.0.50727.8981; 4.7.0 < 4.7.04137.03; 4.8.0 < 4.8.04798.02; 4.8.1 < 4.8.1.09320.02 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-55247 | 14 Oct 2025 | 8.0.0 < 8.0.21; 9.0.0 < 9.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-30399 | 13 Jun 2025 | 8.0.0 < 8.0.17; 9.0.0 < 9.0.6; 17.10.0 < 17.10.16; 17.12.0 < 17.12.9; 17.14.0 < 17.14.5; 17.8.0 < 17.8.22; 7.4.0 < 7.4.11; 7.5.0 < 7.5.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-26646 | 13 May 2025 | 8.0.0 < 8.0.16; 9.0.0 < 9.0.5; 17.0 < Fixed Version 17.13.7; 17.10.0 < 17.10.15; 17.12.0 < 17.12.8; 17.13.0 < 17.13.7; 17.8.0 < 17.8.21 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-21172 | 14 Jan 2025 | 8.0.0 < 8.0.12; 9.0.0 < 9.0.1; 14.0.0 < 14.0.24252.2; 15.9.0 < 15.9.69; 16.11.0 < 16.11.43; 17.10.0 < 17.10.10; 17.12.0 < 17.12.4; 17.6.0 < 17.6.22 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-21173 | 14 Jan 2025 | 8.0.0 < 8.0.12; 9.0.0 < 9.0.1; 17.10.0 < 17.10.10; 17.12.0 < 17.12.4; 17.6.0 < 17.6.22; 17.8.0 < 17.8.17 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-21176 | 14 Jan 2025 | 8.0.0 < 8.0.12; 9.0.0 < 9.0.1; 3.0.0.0 < 10.0.14393.7699; 4.7.0 < 4.7.04126.01; 4.8.0 < 4.8.04775.01; 4.8.1 < 4.8.1.09294.01 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-38229 | 8 Oct 2024 | 8.0.0 < 8.0.10; 17.10 < 17.10.8; 17.11 < 17.11.5; 17.6.0 < 17.6.20; 17.8.0 < 17.8.15 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-38168 | 13 Aug 2024 | 8.0 < 8.0.8; 17.6.0 < 17.6.18; 17.10 < 17.10.6; 17.8.0 < 17.8.13 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-30105 | 9 Jul 2024 | 8.0 < 8.0.7; 7.4.0 < 7.4.4; 17.4.0 < 17.4.21; 17.6.0 < 17.6.17; 17.10 < 17.10.4; 17.8.0 < 17.8.12 | Update to V4.0.700 or later version | Update reference ↗ |
| CVE-2024-30045 | 14 May 2024 | 8.0 < 8.0.5; 7.0.0 < 7.0.19; 17.0 < 17.9.7; 17.4.0 < 17.4.19; 17.6.0 < 17.6.15; 17.8.0 < 17.8.10; 7.4.0 < 7.4.3 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-0057 | 9 Jan 2024 | 8.0 < 8.0.1; 7.0.0 < 7.0.15; 6.0.0 < 6.0.26; 17.2.0 < 17.2.23; 16.11.0 < 16.11.34; 17.4.0 < 17.4.15; 17.6.0 < 17.6.11; 17.8.0 < 17.8.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.