dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2026-50682

HIGH · 7.1 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.19044.7548 / 10.0.19045.7548 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
Out-of-bounds read in Windows Active Directory allows an authorized 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 out-of-bounds read vulnerability in Windows Active Directory allows an authenticated attacker to cause a denial of service by sending specially crafted network requests to affected AD servers.

MitigationApply the relevant Microsoft security update for Windows Active Directory Domain Controllers as soon as possible, prioritizing internet-facing and high-value domain controllers.

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 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269< 10.0.28000.2525
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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 the server is running Active Directory Domain Services
    Run 'Get-WindowsFeature AD-Domain-Services' in PowerShell on Domain Controllers, or check Services.msc for 'Active Directory Domain Services' is running
    Affected if The server is NOT a Domain Controller, so this vulnerability does not apply
  2. Get the Windows build version
    Run 'winver' or execute 'systeminfo | findstr /C:"OS Version"' in Command Prompt, or use 'Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber' in PowerShell
    Affected if The build version is below the thresholds listed in the affected versions for your Windows release
  3. Confirm the specific Windows release
    Check if the system is Windows 10 21h2, 10 22h2, Windows 11 24h2/25h2/26h1, Server 2022, or Server 2025 by running 'winver' or checking system information
    Affected if The Windows release matches any of the affected products listed in the CVE
  4. Compare your version against the affected thresholds
    For Windows 10 21h2: verify build < 19044.7548. For Windows 10 22h2: verify build < 19045.7548. For Windows 11 24h2: verify build < 26100.8875. For Windows 11 25h2: verify build < 26200.8875. For Windows 11 26h1: verify build < 28000.2269 or < 28000.2525. For Server 2022: verify build < 20348.5386. For Server 2025: verify build < 26100.33158
    Affected if Your installed build number falls below the specified threshold for your Windows release and the system is a Domain Controller

You are affected if this system is an Active Directory Domain Controller running a Windows version whose build number is below the threshold for its specific release, making it vulnerable to authenticated remote attackers causing denial of service via specially crafted network requests.

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.19044.7548 / 10.0.19045.7548 / 10.0.20348.5386 or later
Fixed in 10.0.19044.754810.0.19045.754810.0.20348.5386
Interim mitigation

Apply the relevant Microsoft security update for Windows Active Directory Domain Controllers as soon as possible, prioritizing internet-facing and high-value domain controllers.

Recommended fix High confidence

Apply the Microsoft security patch for CVE-2026-50682 targeting the specific Windows version/build listed in the fixed version requirements

  1. Apply the Microsoft security update for CVE-2026-50682 from the Microsoft Security Response Center (msrc.microsoft.com)
  2. For Windows 10 21h2 (build 19044): upgrade to 10.0.19044.7548 or later
  3. For Windows 10 22h2 (build 19045): upgrade to 10.0.19045.7548 or later
  4. For Windows 11 24h2 (build 26100): upgrade to 10.0.26100.8875 or later
  5. For Windows 11 25h2 (build 26200): upgrade to 10.0.26200.8875 or later
  6. For Windows 11 26h1: upgrade to 10.0.28000.2525 or later
  7. For Windows Server 2022: upgrade to 10.0.20348.5386 or later
  8. For Windows Server 2025: upgrade to 10.0.26100.33158 or later
Caveat Standard Windows update process; test in non-production environment before broad deployment

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

Fix this in Windows 10 21h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50682 — 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-50682 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