CVE-2026-32226: .NET Framework Denial of Service Vulnerability

Published Apr 14, 2026
·
Updated

.NET Framework Denial of Service Vulnerability

Other sources

Concurrent execution using shared resource with improper synchronization ('race condition') in .NET Framework allows an unauthorized attacker to deny service over a network.

Microsoft

Affected Software

57 affected componentsFixes available
Microsoft .NET Framework=4.8
Microsoft .NET Framework=4.8
Microsoft .NET Framework=3.5, =4.8
Microsoft .NET Framework=3.5, =4.7.2
Microsoft .NET Framework=4.8
Microsoft .NET Framework=3.5, =4.8
Microsoft .NET Framework=3.5, =4.8.1
Microsoft .NET Framework=3.5, =4.8.1
Microsoft .NET Framework=3.5, =4.8.1
Microsoft .NET Framework=3.5
Microsoft .NET Framework=3.5, =4.8.1
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
Microsoft .NET Framework=3.5
Microsoft .NET Framework=4.8.1
Microsoft .NET Framework=4.7.2
Microsoft .NET Framework=3.5, =4.8
All of the following
Any of the following
Microsoft .NET Framework=3.5
Microsoft .NET Framework=4.7.2
Any of the following
Microsoft Windows 10 1809
Microsoft Windows 10 1809
All of the following
Any of the following
Microsoft .NET Framework=3.5
Microsoft .NET Framework=4.8
Any of the following
Microsoft Windows 10 1809
Microsoft Windows 10 1809
Microsoft Windows 10 1809
Microsoft Windows Server 20h2
All of the following
Microsoft .NET Framework=4.8
Any of the following
Microsoft Windows 10 1607
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
All of the following
Any of the following
Microsoft .NET Framework=3.5
Microsoft .NET Framework=4.8.1
Any of the following
Microsoft Windows 11 26h1
Microsoft Windows 11 26h1
Microsoft Windows Server 2025
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0
Microsoft .NET Framework=3.5
2.0.50727.8982 & 3.0.30729.8976
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
4.7.4141.0
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
4.8.4801.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9181 & 3.0.30729.9165 & 4.8.4801.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9181 & 3.0.30729.9165 & 4.8.4801.0
Microsoft .NET Framework=3.5, =4.7.2
2.0.50727.9068 & 3.0.30729.9065 & 4.7.4141.0
Microsoft .NET Framework=3.5
2.0.50727.8982 & 3.0.30729.8976
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0
Microsoft .NET Framework=4.7.2
2.0.50727.9068 & 3.0.30729.9065 & 4.7.4141.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0
Microsoft .NET Framework=4.8
2.0.50727.9181 & 3.0.30729.9165 & 4.8.4801.0
Microsoft .NET Framework=4.8
2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0
Microsoft .NET Framework=4.8.1
2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9068 & 3.0.30729.9065 & 4.8.4801.0
Microsoft .NET Framework=4.8
4.8.4801.0
Microsoft .NET Framework=4.8
4.8.4801.0
Microsoft .NET Framework=4.8
4.8.4801.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8982 & 3.0.30729.8976Patch KB5082398
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0Patch KB5082417
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0Patch KB5082425
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0Patch KB5082424
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0Patch KB5082419
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.7.4141.0Patch KB5082402
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4801.0Patch KB5082400
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.4801.0Patch KB5082426
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.4801.0Patch KB5082427
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0Patch KB5082420
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9068 & 3.0.30729.9065 & 4.7.4141.0Patch KB5082413
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8982 & 3.0.30729.8976Patch KB5082406
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0Patch KB5082418
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9068 & 3.0.30729.9065 & 4.8.4801.0Patch KB5082414
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4801.0Patch KB5082404
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4801.0Patch KB5082403
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4801.0Patch KB5082411
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0Patch KB5082421

Event History

Apr 14, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
CVE Published
via MITRE·04:57 PM
Data Sourced
via MITRE·04:57 PM
DescriptionSeverity
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-32226?

CVE-2026-32226 has a high severity rating due to its potential to cause denial of service through improper synchronization.

2

How do I fix CVE-2026-32226?

To fix CVE-2026-32226, update your .NET Framework to the latest patched version provided by Microsoft.

3

Which versions of .NET Framework are affected by CVE-2026-32226?

CVE-2026-32226 affects .NET Framework versions 3.5, 4.7.2, 4.8, and 4.8.1.

4

Can CVE-2026-32226 be exploited remotely?

Yes, CVE-2026-32226 allows an unauthorized attacker to exploit the vulnerability remotely over a network.

5

What type of vulnerability is CVE-2026-32226?

CVE-2026-32226 is categorized as a Denial of Service vulnerability resulting from a race condition.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203