dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-32160

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 Push Notifications 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

A race condition vulnerability exists in Windows Push Notifications where improper synchronization of shared resources allows a locally authorized attacker to exploit timing windows and elevate their privileges to higher integrity levels.

MitigationApply the relevant Microsoft security update for Windows Push Notifications when available, as this is a privilege escalation vulnerability requiring patch deployment.

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 number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if The build number is lower than the fixed version for your specific Windows release (e.g., below 10.0.17763.8644 for Windows 10 1809/Server 2019, below 10.0.19044.7184 for Windows 10 21h2, below 10.0.19045.7184 for Windows 10 22h2, below 10.0.22631.6936 for Windows 11 23h2, below 10.0.26100.8246 for
  2. Identify Windows edition
    Run 'systeminfo' or 'winver' to confirm whether the system is Windows 10 (specifying 1809, 21h2, or 22h2), Windows 11 (23h2, 24h2, 25h2, or 26h1), or Windows Server 2019
    Affected if The system matches any of the affected products and versions listed in the CVE (Windows 10 1809, 21h2, 22h2; Windows 11 23h2, 24h2, 25h2, 26h1; or Windows Server 2019) and the build number is below the fixed threshold
  3. Confirm Windows Push Notifications component presence
    Check for the presence of the Windows Push Notification service by reviewing installed Windows components or checking registry key 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PushNotifications' if accessible
    Affected if The Windows Push Notifications component is present on the system (this is a default component in affected Windows versions)

The environment is affected if the system runs any of the listed Windows 10 or Windows 11 versions or Windows Server 2019 with a build number lower than the corresponding fixed version, since the vulnerability exists in the Windows Push Notifications feature present in those releases.

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 update for Windows Push Notifications when available, as this is a privilege escalation vulnerability requiring patch deployment.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.8644 | Windows 10 21h2: 10.0.19044.7184 | Windows 10 22h2: 10.0.19045.7184 | Windows 11 23h2: 10.0.22631.6936 | Windows 11 24h2: 10.0.26100.8246 | Windows 11 25h2: 10.0.26200.8246 | Windows 11 26h1: 10.0.28000.1836 | Windows Server 2019: 10.0.17763.8644

  1. Check current Windows version by running 'winver' or 'systeminfo' from command prompt
  2. Open Windows Settings and navigate to 'Update & Security' > 'Windows Update'
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the update containing the fix for CVE-2026-32160 is installed (typically labeled as a Security Update for Windows)
  5. Restart the system when prompted to complete the installation
  6. Verify the installed version matches or exceeds the fixed version for your Windows edition (e.g., 10.0.17763.8644 for Windows 10 1809/Server 2019, 10.0.19044.7184 for Windows 10 21h2, etc.)
Caveat Standard Windows update process; no expected breaking changes for this security patch

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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