dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50356

HIGH · 7.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
72/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
Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Windows App Store allows an authorized attacker to elevate privileges 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

A race condition vulnerability exists in the Microsoft Windows App Store where concurrent execution with improper synchronization on a shared resource allows a locally authorized attacker to elevate privileges. The attacker exploits timing-sensitive operations to gain higher-level access than initially granted.

MitigationApply Microsoft security patches for the Windows App Store race condition vulnerability. Organizations should prioritize patching given the local privilege escalation vector and high severity rating.

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.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
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 2016Operating system
Affected:< 10.0.14393.9339

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/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 and build number
    Open Command Prompt or PowerShell and run 'winver' or 'Get-ComputerInfo | Select WindowsVersion,OsBuildNumber,OsHardwareAbstractionLayer' to retrieve the exact Windows version and build number
    Affected if The version/build is lower than any of these thresholds: 14393.9339 (Win 10 1607/Server 2016), 17763.9020 (Win 10 1809), 19044.7548 (Win 10 21h2), 19045.7548 (Win 10 22h2), 26100.8875 (Win 11 24h2), 26200.8875 (Win 11 25h2), or 28000.2269/28000.2525 (Win 11 26h1)
  2. Confirm Windows App Store is installed
    Run 'Get-AppxPackage -Name Microsoft.WindowsStore | Select-Object Name,Version,PackageFullName' in PowerShell to check if the Windows Store app is present on the system
    Affected if The App Store package (Microsoft.WindowsStore) is installed and present on the system - the vulnerability exists within this component
  3. Verify local user account context
    Run 'whoami /all' or 'Get-LocalUser' in PowerShell to confirm you are running under a locally authorized user account rather than a domain administrator
    Affected if You are a local user with standard or elevated local privileges - the attacker needs local authorization to exploit this race condition

Your system is affected if it runs a Windows version below the specified build thresholds AND has the Windows App Store installed, allowing a locally authorized user to potentially exploit the race condition for privilege escalation.

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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply Microsoft security patches for the Windows App Store race condition vulnerability. Organizations should prioritize patching given the local privilege escalation vector and high severity rating.

Recommended fix High confidence

Windows 10 1607/Server 2016: 10.0.14393.9339+ | Windows 10 1809: 10.0.17763.9020+ | 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+

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Download the latest Windows updates from Windows Update or use the Windows Installation Assistant/ISO for a clean install
  3. For Windows 10 1607/Server 2016: Upgrade to version 10.0.14393.9339 or later
  4. For Windows 10 1809: Upgrade to version 10.0.17763.9020 or later
  5. For Windows 10 21h2: Upgrade to version 10.0.19044.7548 or later
  6. For Windows 10 22h2: Upgrade to version 10.0.19045.7548 or later
  7. For Windows 11 24h2: Upgrade to version 10.0.26100.8875 or later
  8. For Windows 11 25h2: Upgrade to version 10.0.26200.8875 or later
Caveat Standard Windows update applies; ensure backups of critical data before applying major version upgrades

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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