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

Windows Active Directory Federation Services Denial of Service Vulnerability

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

Summary

Loop with unreachable exit condition ('infinite loop') in Active Directory Federation Services (AD FS) allows an unauthorized attacker to deny service over a network.

Products covered

  • Windows 10 Version 1809 for 32-bit Systems

  • Windows 10 Version 1809 for x64-based Systems

  • Windows Server 2019

  • Windows Server 2019 (Server Core installation)

  • Windows Server 2022

  • Windows Server 2025 (Server Core installation)

  • Windows Server 2025

  • Windows 10 Version 1607 for 32-bit Systems

Show 53 more products
  • Windows 10 Version 1607 for x64-based Systems

  • Windows Server 2016

  • Windows Server 2016 (Server Core installation)

  • Windows Server 2012 R2

  • Windows Server 2012 R2 (Server Core installation)

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

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

  • Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems

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

  • Microsoft .NET Framework 4.8 on Windows Server 2016

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

  • Microsoft .NET Framework 4.8 on Windows Server 2012

  • 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 4.8 on Windows Server 2012 R2 (Server Core installation)

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

  • 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 Server 2019

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

  • 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 21H2 for 32-bit 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 x64-based Systems

  • 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 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 Server 2019

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation)

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

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

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2016

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2016 (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 (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 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2 (Server Core installation)

  • 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 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 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 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

Remediation

Install KB5099538. Install KB5099540. Install KB5099536. Install KB5099535. Install KB5099444. Install KB5101002. Install KB5101007. Install KB5101009. Install KB5101011. Install KB5101008. Install KB5101010. Install KB5101006. Install KB5100989. Install KB5100990. Install KB5100991. Install KB5101005. Install KB5101000. Install KB5100998. Install KB5101004. Install KB5101001.

Vendor-listed fixes

  • 10.0.17763.9020

  • 10.0.20348.5386

  • 10.0.26100.33158

  • 10.0.14393.9339

  • 6.3.9600.23291

  • 4.8.9340.0

  • 4.8.4803.0

  • 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0

Show 6 more fixes
  • 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0

  • 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0

  • 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0

  • 4.7.4143.0

  • 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0

  • 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.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.