CVE-2026-58280
.NET Denial of Service Vulnerability
Monitor this CVE ↗Full CVE monitoring on Pro and Business
What happened?
See the source record for the publisher’s description.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| .NET 10.0 runtimeMicrosoft | affected: 10.0.0 to < 10.0.13 | See vendor advisory |
| .NET 11.0 runtimeMicrosoft | affected: 11.0.0 to < 11.0.0-rc.2 | See vendor advisory |
| .NET 8.0 runtimeMicrosoft | affected: 8.0.0 to < 8.0.32 | See vendor advisory |
| .NET 9.0 runtimeMicrosoft | affected: 9.0.0 to < 9.0.21 | See vendor advisory |
| Microsoft .NET Framework 3.5Microsoft | affected: 3.5.0 to < 2.0.50727.9188 AND 3.0.30729.9171 | See vendor advisory |
| Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2Microsoft | affected: 3.0.0.0 to < 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0 | See vendor advisory |
| Microsoft .NET Framework 3.5 AND 4.7.2Microsoft | affected: 4.7.0 to < 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 | See vendor advisory |
| Microsoft .NET Framework 3.5 AND 4.8Microsoft | affected: 4.8.0 to < 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0 | See vendor advisory |
| Microsoft .NET Framework 3.5 AND 4.8.1Microsoft | affected: 4.8.1 to < 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 | See vendor advisory |
| Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2Microsoft | affected: 4.7.0 to < 4.7.4150.0 | See vendor advisory |
| Microsoft .NET Framework 4.8Microsoft | affected: 4.8.0 to < 4.8.4811.0 | See vendor advisory |
| Microsoft .NET Framework 4.8.1Microsoft | affected: 4.8.0.0 to < 4.8.9363.0 | See vendor advisory |
| Microsoft Visual Studio 2022 version 17.14Microsoft | affected: 17.14.0 to < 17.14.42 | See vendor advisory |
| Microsoft Visual Studio 2026 version 18.10Microsoft | affected: 18.10.0 to < 18.10.4 | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.