CVE-2022-26832
.NET Framework Denial of Service Vulnerability
HIGH
7.5
CVSS Score
Published: April 15, 2022 at 07:05 PM UTC
Updated: June 17, 2026 at 04:35 AM UTC
12 products affected across 1 vendor.NET Framework.netWindows Server 2016
Using Microsoft .NET Framework 3.5 AND 4.8 by Microsoft?
Get instant alerts when new vulnerabilities affect Microsoft .NET Framework 3.5 AND 4.8 - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 4%
Description
.NET Framework Denial of Service Vulnerability
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
2.0.0 ≤ v < 2.0.50727.89623.0.0 ≤ v < 2.0.50727.89623.5.0 ≤ v < 6.1.50727.89623.5.0 ≤ v < publication4.7.0 ≤ v < 4.7.3930.024.8.0 ≤ v < 4.8.04494.034.8.0 ≤ v < 4.8.4494.03
Affected range stops below 2.0.50727.8962, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.7.3930.02, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.8.04494.03, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.8.4494.03, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.50727.8962, so it looks safe — our inference, not a vendor statement
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
2.0.0 ≤ v < 2.0.50727.89623.0.0 ≤ v < 2.0.50727.89623.0.0.0 ≤ v < 10.0.14393.50663.5.0 ≤ v < 6.1.50727.89623.5.0 ≤ v < publication4.0.0.0 ≤ v < 4.0.52732.367324.0.0.0 ≤ v < 4.7.03930.024.7.0 ≤ v < 4.7.3930.024.8.0 ≤ v < 4.8.04494.034.8.0 ≤ v < 4.8.4494.032.0 sp22.0.03.0 sp23.0.03.0.0.03.53.5.03.5.14.0.0.04.5.24.64.6.14.6.24.74.7.04.7.14.7.24.84.8.0
Affected range stops below 10.0.14393.5066, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.0.50727.8962, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.52732.36732, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.7.03930.02, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.7.3930.02, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.8.04494.03, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.8.4494.03, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.50727.8962, so it looks safe — our inference, not a vendor statement
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
microsoft-windows-10 (environment) · microsoft-windows-11 (environment) · microsoft-windows-7 (environment) · microsoft-windows-8-1 (environment) · microsoft-windows-rt-8-1 (environment) · microsoft-windows-server-2008 (environment) · microsoft-windows-server-2012 (environment) · microsoft-windows-server-2016 (environment) · microsoft-windows-server-2019 (environment) · microsoft-windows-server-2022 (environment)
Windows 10· Microsoftdevice
80%All versions
Windows 11· Microsoftdevice
80%All versions
Windows 7· Microsoftdevice
80%All versions
Windows 8-1· Microsoftdevice
80%All versions
80%
All versions
80%
All versions
80%
All versions
80%
All versions
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (2)
Vendor Advisory
Source: [email protected]
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-26832PatchVendor Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-26832CVSS
7.5HIGHmicrosoft
Vector?
Quick Info
StatusMODIFIED
CWE
NVD-CWE-noinfo
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card