CVE-2026-50304: Windows Active Directory Federation Services Denial of Service Vulnerability

Published Jul 14, 2026
·
Updated

Stack-based buffer overflow in Active Directory Federation Services allows an unauthorized attacker to deny service over a network.

Other sources

Windows Active Directory Federation Services Denial of Service Vulnerability

— Microsoft

Affected Software

45 affected componentsFixes available
Microsoft Active Directory Federation Services
Microsoft Windows 10=1809
10.0.17763.9020
Microsoft Windows Server 2025<10.0.26100.33158
10.0.26100.33158
Microsoft Windows Server 2025<10.0.26100.33158
10.0.26100.33158
Microsoft Windows Server 2019<10.0.17763.9020
10.0.17763.9020
Microsoft Windows Server 2016<10.0.14393.9339
10.0.14393.9339
Microsoft Windows Server 2022<10.0.20348.5386
10.0.20348.5386
Microsoft Windows 10=1607
10.0.14393.9339
Microsoft Windows Server 2012 R2<6.3.9600.23291
6.3.9600.23291
Microsoft Windows 10=1607
10.0.14393.9339
Microsoft Windows Server 2019<10.0.17763.9020
10.0.17763.9020
Microsoft Windows Server 2016<10.0.14393.9339
10.0.14393.9339
Microsoft Windows Server 2012<6.2.9200.26226
6.2.9200.26226
Microsoft Windows Server 2012 R2<6.3.9600.23291
6.3.9600.23291
Microsoft Windows Server 2012<6.2.9200.26226
6.2.9200.26226
Microsoft Windows 10=1809
10.0.17763.9020
Microsoft .NET Framework=3.5
2.0.50727.8983 & 3.0.30729.8978
Microsoft .NET Framework=3.5
2.0.50727.8983 & 3.0.30729.8978
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.0
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
4.7.4143.0
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
4.7.4143.0
Microsoft .NET Framework=3.5, =4.7.2
2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0
Microsoft .NET Framework=3.5, =4.7.2
2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0
Microsoft .NET Framework=4.8
4.8.4803.0
Microsoft .NET Framework=4.8
4.8.4803.0
Microsoft .NET Framework=4.8
4.8.4803.0
Microsoft Windows 10 1607<10.0.14393.9339
Microsoft Windows 10 1607<10.0.14393.9339
Microsoft Windows 10 1809<10.0.17763.9020
Microsoft Windows 10 1809<10.0.17763.9020
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.9339
Microsoft Windows Server 2019<10.0.17763.9020
Microsoft Windows Server 2022<10.0.20348.5386
Microsoft Windows Server 2025<10.0.26100.33158
Microsoft .NET Framework=4.8.1
4.8.9340.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 10.0.17763.9020Patch KB5099538
  2. Upgrade

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

    Fixed in 10.0.26100.33158Patch KB5099536
  3. Upgrade

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

    Fixed in 10.0.14393.9339Patch KB5099535
  4. Upgrade

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

    Fixed in 10.0.20348.5386Patch KB5099540
  5. Upgrade

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

    Fixed in 6.3.9600.23291Patch KB5099444
  6. Upgrade

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

    Fixed in 6.2.9200.26226Patch KB5099445
  7. Upgrade

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

    Fixed in 2.0.50727.8983 & 3.0.30729.8978Patch KB5100985
  8. Upgrade

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

    Fixed in 2.0.50727.8983 & 3.0.30729.8978Patch KB5100984
  9. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.0Patch KB5101003
  10. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168Patch KB5101014
  11. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0Patch KB5101001
  12. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0Patch KB5101004
  13. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0Patch KB5101000
  14. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.0Patch KB5100998
  15. Upgrade

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

    Fixed in 4.7.4143.0Patch KB5100991
  16. Upgrade

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

    Fixed in 4.7.4143.0Patch KB5100990
  17. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0Patch KB5101005
  18. Upgrade

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

    Fixed in 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0Patch KB5099535
  19. Upgrade

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

    Fixed in 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0Patch KB5100989
  20. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0Patch KB5101006
  21. Upgrade

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

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0Patch KB5101010
  22. Upgrade

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

    Fixed in 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0Patch KB5101008
  23. Upgrade

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

    Fixed in 4.8.4803.0Patch KB5101011
  24. Upgrade

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

    Fixed in 4.8.4803.0Patch KB5101009
  25. Upgrade

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

    Fixed in 4.8.4803.0Patch KB5101007
  26. Upgrade

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

    Fixed in 4.8.9340.0Patch KB5101002

Event History

Jul 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·05:06 PM
Data Sourced
via MITRE·05:06 PM
DescriptionSeverity
Data Sourced
via NVD·06:17 PM
RemedyDescriptionSeverityWeaknessAffected 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-50304?

CVE-2026-50304 has a high severity rating of 7.5.

2

How does CVE-2026-50304 affect systems?

CVE-2026-50304 allows an unauthorized attacker to perform a denial of service attack on affected systems.

3

Which systems are impacted by CVE-2026-50304?

CVE-2026-50304 affects various versions of Microsoft Windows, including Windows Server 2012, 2016, 2019, 2022, and Windows 10.

4

What is the cause of the CVE-2026-50304 vulnerability?

The vulnerability in CVE-2026-50304 is caused by a stack-based buffer overflow in Active Directory Federation Services.

5

What steps should be taken to mitigate CVE-2026-50304?

To mitigate CVE-2026-50304, it is essential to update your systems with the latest security patches provided by Microsoft.

Company

Resources

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