dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-32163

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.17763.8644 / 10.0.19044.7184 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows User Interface Core allows an authorized attacker to elevate privileges locally.

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

This is a race condition vulnerability in Windows User Interface Core where improper synchronization of shared resources allows a local authorized attacker to elevate privileges. The vulnerability stems from concurrent execution issues in the UI component that can be exploited to gain higher-level access.

MitigationApply the relevant Microsoft security patch for this vulnerability to all affected Windows systems. Since this is a local privilege escalation, ensure attackers cannot achieve code execution in low-privilege contexts.

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 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836
Windows Server 2019Operating system
Affected:< 10.0.17763.8644

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/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. Check Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the Windows build number
    Affected if The build number displayed is lower than the threshold for your Windows version (17763.8644 for Windows 10 1809/Server 2019, 19044.7184 for Windows 10 21h2, 19045.7184 for Windows 10 22h2, 22631.6936 for Windows 11 23h2, 26100.8246 for Windows 11 24h2, 26200.8246 for Windows 11 25h2, or 28000.1836 f
  2. Confirm Windows edition and build manually
    Run 'ver' in Command Prompt or use PowerShell Get-ItemProperty to query the registry key 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' for CurrentBuild and DisplayVersion
    Affected if CurrentBuild number is less than the affected threshold for your specific Windows release
  3. Identify if the system is a supported affected version
    Cross-reference the detected build number with the affected version ranges provided - note that versions before each cutoff threshold are vulnerable
    Affected if Your installed Windows version and build number fall within any of the listed affected ranges (less than the specified cutoff for your Windows release)

You are affected if your Windows system build number is lower than the cutoff version for your specific Windows release, as this is a local privilege escalation requiring an attacker to already have authenticated access to the system.

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.17763.8644 / 10.0.19044.7184 / 10.0.19045.7184 or later
Fixed in 10.0.17763.864410.0.19044.718410.0.19045.7184
Interim mitigation

Apply the relevant Microsoft security patch for this vulnerability to all affected Windows systems. Since this is a local privilege escalation, ensure attackers cannot achieve code execution in low-privilege contexts.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2026-32163 corresponding to your Windows version (e.g., Windows 10 1809/Server 2019: KBxxxxxxx providing build 10.0.17763.8644 or later)

  1. 1. Identify the current Windows version by opening Settings > System > About or running 'winver' in the Run dialog
  2. 2. Determine which Windows version category your system falls into (e.g., Windows 10 1809, Windows 10 21h2, Windows 11 23h2, etc.)
  3. 3. Check your current build number against the fixed versions: Windows 10 1809/Server 2019 requires build 10.0.17763.8644 or later; Windows 10 21h2 requires build 10.0.19044.7184 or later; Windows 10 22h2 requires build 10.0.19045.7184 or later; Windows 11 23h2 requires build 10.0.22631.6936 or later; Windows 11 24h2 requires build 10.0.26100.8246 or later
  4. 4. Apply the appropriate Windows Security Update (KB) from Microsoft that addresses this vulnerability for your specific Windows version
  5. 5. Restart the system after installing the update
  6. 6. Verify the update was successful by checking Windows Update history or running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update - minimal risk; ensure regular backups and compatibility checks for business-critical applications before applying

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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