CVE-2026-50525: Allocation of resources without limits or throttling in .NET allows an unauthorized attacker to deny service o HIGH 7.5 REMOTE WATCHLIST DOWNGRADE UPGRADE UPGRADE
CVE-2026-50525 is a high-severity flaw (CVSS 7.5) affecting .net framework, .net, visual studio 2022. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Allocation of resources without limits or throttling in .NET allows an unauthorized attacker to deny service over a network.
Why this priority High severity Remotely exploitable, no login, no user action On your watchlist A fixed release or distro patch exists.
Risk facts CVSS score 7.5 (High) Attack vector Network (remote) Attack complexity Low Privileges needed None User interaction None EPSS exploit chance 1.2% (top 33%) CISA exploited list No Weakness CWE-770 Published 2026-07-14 Last modified 2026-07-24
Share: LinkedIn · X · Reddit
Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Timeline 2026-07-14 20:17 UTC Published CVE record published2026-07-24 13:39 UTC Updated Record last modifiedmicrosoft .net framework DOWNGRADE
Affected: 4.8.1 · 4.8 · 4.6.2 · 4.7 · 4.7.1 · 4.7.2 · 3.5
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.5
1. Check installed version
Copy apt-cache policy .net-framework || rpm -q .net-framework || .net-framework --version
2. No fixed release: DOWNGRADE to a release before 3.5 (Debian / Ubuntu)
Copy apt-cache madison .net-framework
sudo apt install .net-framework=<VERSION_BEFORE_3.5>
sudo apt-mark hold .net-framework
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
Copy dnf --showduplicates list .net-framework
sudo dnf downgrade .net-framework-<VERSION_BEFORE_3.5>
sudo dnf versionlock add .net-framework
Downgrade risk
Copy Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Copy Restart the service, and keep the package held until a fixed release ships.
microsoft .net UPGRADE
Affected: >= 8.0.0 and < 8.0.29 · >= 9.0.0 and < 9.0.18 · >= 10.0.0 and < 10.0.6
Fixed in: 8.0.29, 9.0.18, 10.0.6
Safe to downgrade to: a release before 8.0.0
1. Check installed version
Copy apt-cache policy .net || rpm -q .net || .net --version
2. UPGRADE to 8.0.29 (Debian / Ubuntu)
Copy sudo apt update && sudo apt install --only-upgrade .net
2. UPGRADE (RHEL / Amazon Linux / Fedora)
Copy sudo dnf upgrade .net
Note
Copy Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 8.0.0 (Debian / Ubuntu)
Copy apt-cache madison .net
sudo apt install .net=<VERSION_BEFORE_8.0.0>
sudo apt-mark hold .net
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
Copy dnf --showduplicates list .net
sudo dnf downgrade .net-<VERSION_BEFORE_8.0.0>
sudo dnf versionlock add .net
Downgrade risk
Copy Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Copy Restart the service, and keep the package held until a fixed release ships.
microsoft visual studio 2022 UPGRADE
Affected: >= 17.12.0 and < 17.12.22 · >= 17.14.0 and < 17.14.36
Fixed in: 17.12.22, 17.14.36
Safe to downgrade to: a release before 17.12.0
1. Check installed version
Copy apt-cache policy visual-studio-2022 || rpm -q visual-studio-2022 || visual-studio-2022 --version
2. UPGRADE to 17.12.22 (Debian / Ubuntu)
Copy sudo apt update && sudo apt install --only-upgrade visual-studio-2022
2. UPGRADE (RHEL / Amazon Linux / Fedora)
Copy sudo dnf upgrade visual-studio-2022
Note
Copy Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 17.12.0 (Debian / Ubuntu)
Copy apt-cache madison visual-studio-2022
sudo apt install visual-studio-2022=<VERSION_BEFORE_17.12.0>
sudo apt-mark hold visual-studio-2022
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
Copy dnf --showduplicates list visual-studio-2022
sudo dnf downgrade visual-studio-2022-<VERSION_BEFORE_17.12.0>
sudo dnf versionlock add visual-studio-2022
Downgrade risk
Copy Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Copy Restart the service, and keep the package held until a fixed release ships.
microsoft visual studio 2026 UPGRADE
Affected: >= 18.7.0 and < 18.7.4
Fixed in: 18.7.4
Safe to downgrade to: a release before 18.7.0
1. Check installed version
Copy apt-cache policy visual-studio-2026 || rpm -q visual-studio-2026 || visual-studio-2026 --version
2. UPGRADE to 18.7.4 (Debian / Ubuntu)
Copy sudo apt update && sudo apt install --only-upgrade visual-studio-2026
2. UPGRADE (RHEL / Amazon Linux / Fedora)
Copy sudo dnf upgrade visual-studio-2026
Note
Copy Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 18.7.0 (Debian / Ubuntu)
Copy apt-cache madison visual-studio-2026
sudo apt install visual-studio-2026=<VERSION_BEFORE_18.7.0>
sudo apt-mark hold visual-studio-2026
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
Copy dnf --showduplicates list visual-studio-2026
sudo dnf downgrade visual-studio-2026-<VERSION_BEFORE_18.7.0>
sudo dnf versionlock add visual-studio-2026
Downgrade risk
Copy Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Copy Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD ·
CVE Program ·
Report a problem with this page Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems. Quick answers How do I fix CVE-2026-50525? .net framework: downgrade or apply the listed mitigation; .net: upgrade to 8.0.29, 9.0.18, 10.0.6; visual studio 2022: upgrade to 17.12.22, 17.14.36. Exact commands for each OS are on this page.
Is CVE-2026-50525 being exploited? CVE-2026-50525 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-50525 affect? CVE-2026-50525 affects .net framework, .net, visual studio 2022. Severity is high (CVSS 7.5). Allocation of resources without limits or throttling in .NET allows an unauthorized attacker to deny service over a network.
How urgent is CVE-2026-50525? Priority 53/100. High severity; Remotely exploitable, no login, no user action; On your watchlist
Software pages .NET vulnerabilities · Visual Studio vulnerabilities
Related CVEs CVE-2026-23666 HIGH 7.5 DOWNGRADE Improper input validation in .NET Framework allows an unauthorized attacker to deny service over a network.CVE-2026-35433 HIGH 7.3 DOWNGRADE UPGRADE Improper input validation in .NET allows an unauthorized attacker to elevate privileges locally.CVE-2026-96960 HIGH 7.5 UPGRADE DOWNGRADE Asymmetric resource consumption (amplification) in .NET allows an unauthorized attacker to deny service over aCVE-2026-96959 HIGH 7.5 UPGRADE DOWNGRADE Allocation of resources without limits or throttling in .NET allows an unauthorized attacker to deny service oCVE-2026-96958 HIGH 7.5 UPGRADE DOWNGRADE Inefficient algorithmic complexity in .NET allows an unauthorized attacker to deny service over a network.References ← Back to latest CVEs