dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2026-44800

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.22631.7376 / 10.0.26100.8875 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 5 weeks old

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.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1w ago

Surfaced from public web coverage — external links open in a new tab.

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 concurrent execution shares resources without proper synchronization. An authorized local attacker can exploit this improper synchronization to elevate privileges to a higher level, potentially gaining SYSTEM or administrative access.

MitigationApply available Windows security updates for Windows Push Notifications component. Prioritize patching systems with user accounts that could be leveraged for local privilege escalation attacks.

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 11 23h2Operating system
Affected:< 10.0.22631.7376
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2025Operating system
Affected:< 10.0.26100.33158

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 obtain the full build number (e.g., 10.0.22631.xxxx)
    Affected if The build number is lower than 10.0.22631.7376 (23h2), 10.0.26100.8875 (24h2), 10.0.26200.8875 (25h2), 10.0.28000.2269 (26h1), or 10.0.26100.33158 (Server 2025)
  2. Identify Windows edition and branch
    Run 'winver' or check System Properties to confirm if the system is Windows 11 23h2, 24h2, 25h2, 26h1, or Windows Server 2025
    Affected if The system is one of the listed affected versions and the build number is below the corresponding patched build
  3. Verify Windows Push Notification service presence
    Open Services (services.msc) and look for 'Windows Push Notifications User Service' or run 'Get-Service WpnUserService' in PowerShell
    Affected if The Windows Push Notifications User Service exists on the system (this component is required for the vulnerability to be exploitable)

The system is affected if it runs a vulnerable Windows 11 version (23h2/24h2/25h2/26h1) or Windows Server 2025 with a build number below the fixed versions AND has the Windows Push Notifications component present.

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.22631.7376 / 10.0.26100.8875 / 10.0.26100.33158 or later
Fixed in 10.0.22631.737610.0.26100.887510.0.26100.33158
Interim mitigation

Apply available Windows security updates for Windows Push Notifications component. Prioritize patching systems with user accounts that could be leveraged for local privilege escalation attacks.

Recommended fix High confidence

Windows 11 23h2 (10.0.22631.7376+), Windows 11 24h2 (10.0.26100.8875+), Windows 11 25h2 (10.0.26200.8875+), Windows 11 26h1 (10.0.28000.2269+), Windows Server 2025 (10.0.26100.33158+)

  1. Check current Windows version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
  2. For Windows 11 23h2: Upgrade to build 10.0.22631.7376 or later via Windows Update or manually download the update from Microsoft Update Catalog
  3. For Windows 11 24h2: Upgrade to build 10.0.26100.8875 or later via Windows Update or manually download the update from Microsoft Update Catalog
  4. For Windows 11 25h2: Upgrade to build 10.0.26200.8875 or later via Windows Update or manually download the update from Microsoft Update Catalog
  5. For Windows 11 26h1: Upgrade to build 10.0.28000.2269 or later via Windows Update or manually download the update from Microsoft Update Catalog
  6. For Windows Server 2025: Upgrade to build 10.0.26100.33158 or later via Windows Update or Windows Server Update Services (WSUS)
  7. Restart the system after applying the update
  8. Verify the fix by checking the installed build number matches or exceeds the target version
Caveat Standard Windows quality update; may require restart; ensure backup of critical data before applying updates

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

Fix this in Windows 11 23h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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