Back to vendor advisories
Microsoft Security Response CenterCVE-2026-32226

.NET Framework Denial of Service Vulnerability

HighVendor CVSS 5.9 / 10 1 CVE Published Apr 14, 2026 at 7:00 AM UTC

Summary

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

Products covered

  • Microsoft .NET Framework 4.8 on Windows 10 Version 22H2 for x64-based Systems

  • Microsoft .NET Framework 4.8 on Windows 11 Version 22H2 for x64-based Systems

  • Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems

  • Microsoft .NET Framework 4.8 on Windows Server 2012 R2 (Server Core installation)

  • Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)

  • Microsoft .NET Framework 4.8 on Windows Server 2012 R2

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems

Show 47 more products
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 20H2 (Server Core Installation)

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 11 version 21H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for ARM64-based Systems

  • Microsoft .NET Framework 4.7.2 on Windows 10 Version 1809 for 32-bit Systems

  • Microsoft .NET Framework 4.7.2 on Windows 10 Version 1809 for x64-based Systems

  • Microsoft .NET Framework 4.7.2 on Windows 10 Version 1809 for ARM64-based Systems

  • Microsoft .NET Framework 4.8.1 on Windows Server 2022 (Server Core installation)

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 22H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 22H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022, 23H2 Edition (Server Core installation)

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 23H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 24H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 24H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 on Windows Server 2012 R2

  • Microsoft .NET Framework 3.5 on Windows Server 2012 R2 (Server Core installation)

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 26H1 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 26H1 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022 (Server Core installation)

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems

  • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 (Server Core installation)

  • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012

  • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2 (Server Core installation)

  • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022 (Server Core installation)

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 25H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 25H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 23H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 on Windows Server 2012

  • Microsoft .NET Framework 3.5 on Windows Server 2012 (Server Core installation)

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025 (Server Core installation)

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025

Remediation

Install KB5082426. Install KB5082424. Install KB5082411. Install KB5082403. Install KB5082404. Install KB5082414. Install KB5082419. Install KB5082413. Install KB5082425. Install KB5082418. Install KB5082420. Install KB5082406. Install KB5082421. Install KB5082427. Install KB5082400. Install KB5082402. Install KB5082417. Install KB5082398.

Vendor-listed fixes

  • 2.0.50727.9181 & 3.0.30729.9165 & 4.8.4801.0

  • 2.0.50727.9181 & 3.0.30729.9165 & 4.8.9332.0

  • 4.8.4801.0

  • 2.0.50727.9068 & 3.0.30729.9065 & 4.8.4801.0

  • 2.0.50727.9068 & 3.0.30729.9065 & 4.7.4141.0

  • 2.0.50727.8982 & 3.0.30729.8976

  • 4.7.4141.0

CVEs in this advisory 1

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  3. Added to SecurityAlert

    We collected the advisory from the official source.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.