dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50324

MEDIUM · 5.9 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An infinite loop vulnerability exists in Active Directory Federation Services (AD FS) where a loop condition cannot be reached or exited, causing the service to become unresponsive. An unauthenticated remote attacker can exploit this to cause a denial of service over the network.

MitigationApply the Microsoft security update for AD FS when available, or implement network-level rate limiting and monitoring to detect and mitigate DoS attempts until the patch can be deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.9339
Windows Server 2019Operating system
Affected:< 10.0.17763.9020
Windows Server 2022Operating system
Affected:< 10.0.20348.5386
Windows Server 2025Operating system
Affected:< 10.0.26100.33158

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AD FS is installed
    Open PowerShell and run: Get-WindowsFeature -Name ADFS-Federation. Or check for the existence of the ADFS service in Services.msc
    Affected if AD FS role is not installed - the system is not affected. If installed, continue to next check.
  2. Check Windows version
    Run 'winver' from command prompt or run 'systeminfo' and look at the OS Version / OS build number
    Affected if The build number falls below the threshold for your version: 10.0.14393.9339 (1607/2016), 10.0.17763.9020 (1809/2019), 10.0.20348.5386 (2022), 10.0.26100.33158 (2025), or any version of Server 2012/R2 - you may be affected.
  3. Confirm AD FS service is running
    Run 'Get-Service adfssrv' in PowerShell or open Services.msc and locate Active Directory Federation Services
    Affected if If the service is stopped, the vulnerability is not currently exploitable, but the unpatched version is still present.
  4. Check ADFS build version
    Run Get-AdfsProperties in PowerShell, or check the ADFS event log for the version information, or review the installed Windows update history for KB5003635 or subsequent AD FS patches
    Affected if The installed ADFS version is lower than the patched build for your Windows version.

You are affected if AD FS is installed and your Windows build number is below the specified threshold for your version, meaning the service can be exploited for denial of service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.9339 / 10.0.17763.9020 / 10.0.20348.5386 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.20348.5386
Interim mitigation

Apply the Microsoft security update for AD FS when available, or implement network-level rate limiting and monitoring to detect and mitigate DoS attempts until the patch can be deployed.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9339+ | Windows 10 1809: 10.0.17763.9020+ | Windows Server 2016: 10.0.14393.9339+ | Windows Server 2019: 10.0.17763.9020+ | Windows Server 2022: 10.0.20348.5386+ | Windows Server 2025: 10.0.26100.33158+ | Windows Server 2012 R2: No fix available

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Confirm AD FS (Active Directory Federation Services) is installed on the affected server
  3. For Windows 10 1607: Upgrade to build 10.0.14393.9339 or later via Windows Update or Microsoft Update Catalog
  4. For Windows 10 1809: Upgrade to build 10.0.17763.9020 or later via Windows Update or Microsoft Update Catalog
  5. For Windows Server 2016: Upgrade to build 10.0.14393.9339 or later via Windows Update or Microsoft Update Catalog
  6. For Windows Server 2019: Upgrade to build 10.0.17763.9020 or later via Windows Update or Microsoft Update Catalog
  7. For Windows Server 2022: Upgrade to build 10.0.20348.5386 or later via Windows Update or Microsoft Update Catalog
  8. For Windows Server 2025: Upgrade to build 10.0.26100.33158 or later via Windows Update or Microsoft Update Catalog
Caveat Standard security updates typically have minimal breaking changes; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50324 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data