dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-49170

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.17763.9020 / 10.0.19044.7548 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
Insufficient granularity of access control in Windows StateRepository API 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 local privilege escalation vulnerability in the Windows StateRepository API. The issue stems from insufficient granularity of access control checks, allowing an already authorized (but low-privilege) local attacker to manipulate the API in ways that enable elevation to higher privileges.

MitigationApply the relevant Microsoft security patch for this vulnerability. If patches are unavailable, consider restricting user access to the StateRepository service and monitoring for suspicious API calls.

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 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 2019Operating system
Affected:< 10.0.17763.9020
Windows Server 2022Operating system
Affected:< 10.0.20348.5386

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

CVSS:3.1/AV:L/AC:L/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 against affected ranges
    Run 'winver' from command prompt or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build number. Alternatively, run 'ver' command to get the build version.
    Affected if The installed build number is lower than any of these thresholds: 17763.9020 (Win10 1809/Server 2019), 19044.7548 (Win10 21h2), 19045.7548 (Win10 22h2), 26100.8875 (Win11 24h2), 26200.8875 (Win11 25h2), 28000.2269 or 28000.2525 (Win11 26h1), 20348.5386 (Server 2022).
  2. Verify StateRepository service exists and is running
    Open PowerShell and run 'Get-Service StateRepository' to check the service status. Also verify the service executable exists at: C:\Windows\System32\StateRepository.Service.exe
    Affected if The StateRepository service is present and running on the system, which provides the attack surface for this vulnerability.
  3. Check for installed security updates addressing this CVE
    Run 'Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20' in PowerShell to list recent patches. Look for KB entries that correspond to the CVE-2026-49170 security update for your Windows version.
    Affected if No matching security update is installed, meaning the system remains unpatched for this vulnerability.
  4. Review user permissions to StateRepository service
    Use 'icacls C:\Windows\System32\StateRepository.Service.exe' in command prompt to check which users/groups have execute or modify permissions on the service binary.
    Affected if Non-admin users or low-privilege accounts have excessive permissions (such as Modify, Write, or Full Control) on the StateRepository service executable.

A system is affected if it runs a Windows version within the affected build ranges AND has the StateRepository service enabled AND lacks the corresponding security patch for CVE-2026-49170.

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.17763.9020 / 10.0.19044.7548 / 10.0.19045.7548 or later
Fixed in 10.0.17763.902010.0.19044.754810.0.19045.7548
Interim mitigation

Apply the relevant Microsoft security patch for this vulnerability. If patches are unavailable, consider restricting user access to the StateRepository service and monitoring for suspicious API calls.

Recommended fix High confidence

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 2019: 10.0.17763.9020 | Windows Server 2022: 10.0.20348.5386

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify which affected version family your system belongs to (e.g., Windows 10 22h2, Windows 11 24h2, Windows Server 2022)
  3. Open Windows Settings > Update & Security > Windows Update
  4. Click 'Check for updates' and install all available security updates
  5. Alternatively, manually download the specific security update from the Microsoft Update Catalog for your Windows version
  6. Restart the system after updates are installed
  7. Verify the build number matches or exceeds the fixed version (e.g., 10.0.17763.9020 for Windows 10 1809/Server 2019)
Caveat Standard Windows update risks apply - review compatibility for line-of-business applications before deploying

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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