dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2026-32181

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.19044.7184 / 10.0.19045.7184 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Improper privilege management in Microsoft Windows allows an authorized attacker to deny service 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

Improper privilege management in Microsoft Windows allows an authorized attacker to cause a local denial of service. The vulnerability stems from how the OS handles privilege assignments or checks, enabling a local authenticated user to render a system or service unavailable.

MitigationApply Microsoft security updates promptly when available. Follow least-privilege principles to limit user permissions. Restrict local administrative access to only necessary personnel.

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.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 2022Operating system
Affected:< 10.0.20348.5020
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.2274

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Determine Windows build number
    Open Command Prompt or PowerShell and run: winver or systeminfo | findstr /B /C:"OS Version"
    Affected if The displayed build number falls below the threshold for your Windows version (e.g., below 19044.7184 for Win10 22h2, below 22631.6936 for Win11 23h2, etc.)
  2. Identify exact Windows edition and version
    Run 'winver' to see the full version string (e.g., 21H2, 22H2, 23H2, 24H2) and match it to the affected version ranges provided in the CVE advisory
    Affected if The identified edition and build combination is listed in the affected products with a version lower than the fixed build number
  3. Check systeminfo for full build details
    Run 'systeminfo' and locate the OS Name and OS Version fields to confirm the exact Windows version and build number
    Affected if The OS Version field shows a build number lower than the minimum fixed build for that Windows release line
  4. Verify Windows Server version if applicable
    For Windows Server systems, run 'winver' or check System Properties to identify the Server version (2022, 2022 23h2) and its build number
    Affected if Running Windows Server 2022 (build < 10.0.20348.5020) or Windows Server 2022 23h2 (build < 10.0.25398.2274)
  5. Confirm user account type
    Check if the account querying the system is a local authenticated user by running 'whoami /groups' or checking account type in Computer Management
    Affected if The vulnerability requires a local authenticated user to exploit; however, detection focuses on whether the system version is vulnerable regardless of attacker presence

A system is affected if its Windows build number is lower than the minimum fixed version for its specific Windows release (10.0.19044.7184 for Win10 21h2, 10.0.19045.7184 for Win10 22h2, 10.0.22631.6936 for Win11 23h2, 10.0.26100.8246 for Win11 24h2, 10.0.26200.8246 for Win11 25h2, 10.0.28000.1836 for Win11 26h1, 10.0.20348.5020 for Server 2022, or 10.0.25398.2274 for Server 2022 23h2).

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.7184 / 10.0.19045.7184 / 10.0.20348.5020 or later
Fixed in 10.0.19044.718410.0.19045.718410.0.20348.5020
Interim mitigation

Apply Microsoft security updates promptly when available. Follow least-privilege principles to limit user permissions. Restrict local administrative access to only necessary personnel.

Recommended fix High confidence

Install the Windows security update that patches to the build number at or above the threshold for your specific Windows version (10.0.19044.7184, 10.0.19045.7184, 10.0.22631.6936, 10.0.26100.8246, 10.0.26200.8246, 10.0.28000.1836, 10.0.20348.5020, or 10.0.25398.2274 depending on edition)

  1. Identify the current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Build"'
  2. Determine which Windows version and build you are running (10 21h2, 10 22h2, 11 23h2, 11 24h2, 11 25h2, 11 26h1, Server 2022, or Server 2022 23h2)
  3. Open Windows Update by going to Settings > Update & Security > Windows Update, or for Server use Server Manager > Local Server > Windows Update
  4. Click 'Check for updates' to download and install the latest security updates
  5. Alternatively, download the specific update from the Microsoft Update Catalog (catalog.update.microsoft.com) by searching for the KB number associated with this CVE from MSRC
  6. After installation, restart the system when prompted
  7. Verify the installation was successful by checking the new OS build version matches or exceeds: 10.0.19044.7184 (Win10 21h2), 10.0.19045.7184 (Win10 22h2), 10.0.22631.6936 (Win11 23h2), 10.0.26100.8246 (Win11 24h2), 10.0.26200.8246 (Win11 25h2), 10.0.28000.1836 (Win11 26h1), 10.0.20348.5020 (Server 2022), or 10.0.25398.2274 (Server 2022 23h2)
Caveat Standard Windows security update with minimal risk; test in staging environment before production deployment as with any patch

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

Fix this in Windows 10 21h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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