dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-26167

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 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 authenticated attacker to exploit timing windows and achieve local privilege escalation. The vulnerability stems from concurrent access to shared state without proper locking mechanisms.

MitigationApply the Microsoft security update for CVE-2026-26167 once released. Until then, restrict local administrative privileges and monitor for unusual process behavior related to notification services.

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 1607Operating system
Affected:< 10.0.14393.9060
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

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 version build number
    Run 'winver' or execute 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' to retrieve the build number. Compare against the affected version thresholds: Windows 10 1607 requires 10.0.14393.9060, 1809 requires 10.0.17763.8644, 21h2 requires 10.0.19044.7184, 22h2 requires 10.0.19045.7184. Windows 11 23h2 requires 10.0.22631.6936, 24h2 requires 10.0.26100.8246, 25h2 requires 10.0.26200.8246, 26h1 requires 10.0.28000.1836.
    Affected if The installed build number is lower than the required patch version for your specific Windows release.
  2. Verify Windows Push Notifications service status
    Open Services (services.msc) and locate 'Windows Push Notifications' or run 'Get-Service -Name wpnService' via PowerShell to check if the service exists and its current running state.
    Affected if The Windows Push Notifications service is installed and running on the system.
  3. Confirm system is unpatched for CVE-2026-26167
    Run 'powershell Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Select-Object HotFixID,InstalledOn' to list installed security updates. Search for any update specifically addressing CVE-2026-26167 or dated after the vulnerability disclosure date.
    Affected if No security update for CVE-2026-26167 is installed and the Windows version falls within the affected ranges.

You are affected if your Windows version build is below the threshold for your specific release AND the Windows Push Notifications service is present, and no CVE-2026-26167 security update has been applied.

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.14393.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply the Microsoft security update for CVE-2026-26167 once released. Until then, restrict local administrative privileges and monitor for unusual process behavior related to notification services.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9060 or later | Windows 10 1809: 10.0.17763.8644 or later | Windows 10 21h2: 10.0.19044.7184 or later | Windows 10 22h2: 10.0.19045.7184 or later | Windows 11 23h2: 10.0.22631.6936 or later | Windows 11 24h2: 10.0.26100.8246 or later | Windows 11 25h2: 10.0.26200.8246 or

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows version and build you are running from the affected versions list
  3. Apply the appropriate Microsoft Security Update for CVE-2026-26167 from Windows Update or the Microsoft Update Catalog
  4. After installation, restart the system to ensure the patch is fully applied
  5. Verify the installed build matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update - no expected breaking changes for most users; ensure regular backups before any system updates

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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