dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2026-50434

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.19044.7548 / 10.0.19045.7548 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Exposure of sensitive information to an unauthorized actor in Windows Push Notifications allows an authorized attacker to disclose information locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo 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

This is a local information disclosure vulnerability in Windows Push Notifications where an authorized attacker can access sensitive information through the notification system. The attack requires local access and the attacker must have some level of authorized access to the system.

MitigationApply the relevant Microsoft security update for Windows Push Notifications when available. Ensure systems are patched through standard Windows Update processes.

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.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
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< 10.0.28000.2525
Windows Server 2022Operating system
Affected:< 10.0.20348.5386
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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows version and build number
    Affected if The build number is below 19044.7548 for Windows 10 21h2, below 19045.7548 for Windows 10 22h2, below 26100.8875 for Windows 11 24h2, below 26200.8875 for Windows 11 25h2, below 28000.2269 or 28000.2525 for Windows 11 26h1, below 20348.5386 for Windows Server 2022, or below 26100.33158 for Windows S
  2. Verify Windows Push Notifications service exists
    Run 'Get-Service WpnUserService' in PowerShell or check Services.msc for 'Windows Push Notifications User Service'
    Affected if The Windows Push Notifications User Service is present on the system (default enabled component)
  3. Confirm local access context
    Review system access logs and user session data to determine if untrusted local users or processes have access to the system
    Affected if Multiple users have local access or the system hosts untrusted local accounts

You are affected if your Windows build number falls below the fixed version for your specific Windows release and Windows Push Notifications User Service is enabled on the 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.19044.7548 / 10.0.19045.7548 / 10.0.20348.5386 or later
Fixed in 10.0.19044.754810.0.19045.754810.0.20348.5386
Interim mitigation

Apply the relevant Microsoft security update for Windows Push Notifications when available. Ensure systems are patched through standard Windows Update processes.

Recommended fix High confidence

Windows 10 21h2: 10.0.19044.7548+ | Windows 10 22h2: 10.0.19045.7548+ | Windows 11 24h2: 10.0.26100.8875+ | Windows 11 25h2: 10.0.26200.8875+ | Windows 11 26h1: 10.0.28000.2525+ | Windows Server 2022: 10.0.20348.5386+ | Windows Server 2025: 10.0.26100.33158+

  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 Windows Update: For Windows 10 21h2, update to build 10.0.19044.7548 or later
  4. For Windows 10 22h2, update to build 10.0.19045.7548 or later
  5. For Windows 11 24h2, update to build 10.0.26100.8875 or later
  6. For Windows 11 25h2, update to build 10.0.26200.8875 or later
  7. For Windows 11 26h1, update to build 10.0.28000.2525 or later
  8. For Windows Server 2022, update to build 10.0.20348.5386 or later
Caveat Standard Windows security update - minimal risk; standard restart required

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

Fix this in Windows 10 21h2 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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