dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-49784

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 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

This is a race condition vulnerability in the Microsoft Windows App Store where improper synchronization of shared resources allows an authorized local attacker to elevate privileges. The vulnerability occurs when concurrent operations access shared state without proper locking or atomic operations, potentially allowing manipulation of privilege levels during the race window.

MitigationApply Microsoft's official security patch for this vulnerability when available. Until then, limit local access to trusted users only and monitor for any suspicious processes interacting with the Windows App Store service.

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 build version
    Run 'winver' from command prompt or 'systeminfo' and locate the 'OS Build' or 'Build' number shown (for example: 10.0.19045.xxxx)
    Affected if The build number is lower than any of these thresholds: 14393.9339 (Win10 1607/Server 2016), 17763.9020 (Win10 1809), 19044.7548 (Win10 21h2), 19045.7548 (Win10 22h2), 26100.8875 (Win11 24h2), 26200.8875 (Win11 25h2), or 28000.2269/28000.2525 (Win11 26h1)
  2. Identify Windows product edition
    Run 'winver' or check System Properties to determine if the system is Windows 10 (1607, 1809, 21h2, or 22h2), Windows 11 (24h2, 25h2, or 26h1), or Windows Server 2016
    Affected if The system matches any of the affected product versions listed in the CVE and the build is below the corresponding threshold from step 1
  3. Verify Windows App Store component is present
    Check if the Windows Store App is installed by looking for 'Microsoft.WindowsStore' in the registry at 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Store' or by attempting to locate the Store app in the Start menu
    Affected if The Windows App Store is installed and present on the system (the vulnerability exists in this component)
  4. Confirm local user context for exploitation
    Understand that this is a local privilege escalation requiring an authorized local user account. No remote detection method exists for active exploitation, but the vulnerability is only exploitable when an attacker has local access to the machine
    Affected if The system meets version criteria AND untrusted local users have access to the machine

You are affected if your Windows version matches one of the listed products and your build number falls below the corresponding threshold, and the Windows App Store component 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.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's official security patch for this vulnerability when available. Until then, limit local access to trusted users only and monitor for any suspicious processes interacting with the Windows App Store service.

Recommended fix Moderate confidence

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

  1. 1. Identify the current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. 2. Determine if your current build is below the fixed version for your Windows release
  3. 3. Open Windows Update Settings: Start > Settings > Update & Security > Windows Update
  4. 4. Click 'Check for updates' to retrieve the latest security patches
  5. 5. Install the KB patch associated with this CVE (check Microsoft Security Response Center for the specific KB number)
  6. 6. Restart the system after the update is installed
  7. 7. Verify the patch was applied by checking the installed updates: Run 'Get-HotFix' in PowerShell or view installed updates in Control Panel
Caveat Standard Windows security update; no expected breaking changes for this patch

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,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 $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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