dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-32158

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 escalate privileges. The vulnerability stems from concurrent execution issues in the notification system component.

MitigationApply Microsoft security updates for Windows Push Notifications as they become available through Windows Update. Verify the patch deployment across affected systems.

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
    Run 'winver' from command prompt or check 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' or query registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuildNumber
    Affected if Build number is lower than the threshold for your Windows version (17763 for 1809/Server 2019, 19044 for 21h2, 19045 for 22h2, 22631 for 23h2, 26100 for 24h2, 26200 for 25h2, 28000 for 26h1)
  2. Identify exact Windows version
    Run 'winver' to see full version string including release year and month (e.g., 21H2, 22H2, 23H2) or check systeminfo for the version details
    Affected if The version falls into an affected branch (1809, 21h2, 22h2, 23h2, 24h2, 25h2, 26h1, or Server 2019) and the build is below the threshold for that branch
  3. Verify Windows Push Notification Service status
    Run 'Get-Service WpnService' in PowerShell or check services.msc for Windows Push Notification Service
    Affected if The service is present and running (the race condition affects this component, so it must be available for exploitation)
  4. Confirm installed KB patches
    Run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' or check Windows Update history for recent security updates
    Affected if No recent security updates are installed that would contain the fix for this vulnerability (the thresholds listed are the fixed versions)

You are affected if your Windows version matches one of the listed branches AND your build number is below the threshold for that branch AND the Windows Push Notification Service is present on your 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 Microsoft security updates for Windows Push Notifications as they become available through Windows Update. Verify the patch deployment across affected systems.

Recommended fix High confidence

Install the appropriate Windows security update from Microsoft Update Catalog that corresponds to your Windows version and builds to the fixed versions listed above

  1. Identify current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine if the current version is below the fixed version for your Windows release
  3. Open Windows Update by pressing Win+I and selecting 'Windows Update'
  4. Click 'Check for updates' and install all available security updates
  5. After installation, restart the computer to apply the updates
  6. Verify the installed version meets or exceeds the fixed version: Windows 10 1809/Server 2019: 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
Caveat Standard Windows security update; no breaking changes expected for typical enterprise or personal use

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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