.net framework vulnerabilities and fixes
Recent CVEs affecting .net framework, with upgrade or downgrade steps. 3 tracked.
.net framework has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-10-13. Highest priority: CVE-2026-96960 (score 52/100).
- CVE-2026-96960 HIGH 7.5 UPGRADE DOWNGRADE Asymmetric resource consumption (amplification) in .NET allows an unauthorized attacker to deny service over a
- CVE-2026-96959 HIGH 7.5 UPGRADE DOWNGRADE Allocation of resources without limits or throttling in .NET allows an unauthorized attacker to deny service o
- CVE-2026-96958 HIGH 7.5 UPGRADE DOWNGRADE Inefficient algorithmic complexity in .NET allows an unauthorized attacker to deny service over a network.
FAQ
How do I fix .net framework vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is .net framework being exploited right now?
None of the tracked .net framework CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which .net framework CVE should I patch first?
CVE-2026-96960 currently ranks highest (52/100): Asymmetric resource consumption (amplification) in .NET allows an unauthorized attacker to deny service over a.