CVE-2026-49165
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 · uneditedUse of uninitialized resource in Microsoft Windows App Store allows an authorized attacker to disclose information locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
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 confidenceThis vulnerability involves the use of an uninitialized resource (likely a variable or memory location) in the Microsoft Windows App Store component. An authorized local attacker could exploit this to disclose sensitive information due to the uninitialized data being returned or accessible.
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< 10.0.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525< 10.0.14393.9339CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows versionRun 'winver' or execute 'Get-ComputerInfo | Select-Object WindowsVersion,OsVersion' in PowerShell to obtain the installed Windows build numberAffected if The version is lower than any of these: 10.0.14393.9339 (Windows 10 1607/Server 2016), 10.0.17763.9020 (Windows 10 1809), 10.0.19044.7548 (Windows 10 21h2), 10.0.19045.7548 (Windows 10 22h2), 10.0.26100.8875 (Windows 11 24h2), 10.0.26200.8875 (Windows 11 25h2), 10.0.28000.2269 or 10.0.28000.2525 (Wi
-
Confirm Windows App Store presenceExecute 'Get-AppxPackage -Name Microsoft.WindowsStore' in PowerShell to determine if the Windows App Store package is installed on the systemAffected if The Get-AppxPackage command returns a valid package (Store is installed); if no result is returned, the component is not present and the system is likely not affected
-
Verify App Store package versionIf the App Store is installed, run 'Get-AppxPackage -Name Microsoft.WindowsStore | Select-Object Name,Version,PackageFullName' to retrieve the exact package versionAffected if The displayed version falls within the vulnerable version range corresponding to the Windows build identified in step 1 (compare against the version thresholds in the affected product list)
-
Check for recent security updatesRun 'Get-HotFix | Where-Object {$_.Description -like "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell to list recently installed security updatesAffected if No security update related to CVE-2026-49165 appears in the installed updates list, indicating the patch has not been applied
The system is affected if it runs a Windows version listed in the affected ranges AND has the Windows App Store installed AND is missing the corresponding security update for CVE-2026-49165
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.933910.0.17763.902010.0.19044.7548
Apply the Microsoft security update for CVE-2026-49165 when available; until then, limit local access to trusted users and monitor for anomalous access patterns to the Windows App Store.
Upgrade to the specific build numbers: 10.0.14393.9339 (Windows 10 1607/Server 2016), 10.0.17763.9020 (Windows 10 1809), 10.0.19044.7548 (Windows 10 21h2), 10.0.19045.7548 (Windows 10 22h2), 10.0.26100.8875 (Windows 11 24h2), 10.0.26200.8875 (Windows 11 25h2), or 10.0.28000.2525 (Windows 11 26h1)
- Identify the current Windows version and build by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
- For Windows 10 1607 and Windows Server 2016: Upgrade to build 10.0.14393.9339 or later via Windows Update or Microsoft Update Catalog
- For Windows 10 1809: Upgrade to build 10.0.17763.9020 or later via Windows Update
- For Windows 10 21h2: Upgrade to build 10.0.19044.7548 or later via Windows Update
- For Windows 10 22h2: Upgrade to build 10.0.19045.7548 or later via Windows Update
- For Windows 11 24h2: Upgrade to build 10.0.26100.8875 or later via Windows Update
- For Windows 11 25h2: Upgrade to build 10.0.26200.8875 or later via Windows Update
- For Windows 11 26h1: Upgrade to build 10.0.28000.2525 or later via Windows Update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49165 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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