dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-57095

HIGH · 7.8 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 →
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
Exposure of sensitive information to an unauthorized actor in Windows Win32K allows an unauthorized 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

This is a local privilege escalation vulnerability in Windows Win32K (the kernel-mode graphics subsystem). The vulnerability allows an unauthorized local attacker to obtain sensitive information and elevate their privileges to higher integrity levels, potentially achieving SYSTEM or equivalent privileges on the affected Windows system.

MitigationApply Microsoft security updates for this vulnerability as soon as they become available through Windows Update or the Microsoft Security Update Guide. Organizations should prioritize patching endpoints given the high-severity rating and local privilege escalation capability.

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.2525
Windows Server 2012Operating system
Affected:all versions= r2

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 installed Windows version and build number
    Open Command Prompt or PowerShell and run: `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` or use PowerShell: `[System.Environment]::OSVersion.Version` and `(Get-ComputerInfo).OsBuildNumber`
    Affected if The build number falls below the safe thresholds: 14393.9339 (1607), 17763.9020 (1809), 19044.7548 (21h2/22h2), 26100.8875 (24h2), 26200.8875 (25h2), or 28000.2525 (26h1)
  2. Confirm Windows 10/11 release branch
    Run `winver` or check Settings > System > About to identify the specific Windows 10 release (1607, 1809, 21h2, 22h2) or Windows 11 release (24h2, 25h2, 26h1)
    Affected if The identified release matches any of the affected versions listed in the CVE and the build number is below the fixed version for that release
  3. Check Windows Server 2012 R2 status
    Run `systeminfo | findstr "Domain"` to confirm if the system is a Windows Server, then run `winver` or check `HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion` in registry to verify it is Server 2012 R2
    Affected if The system is Windows Server 2012 R2 (all versions are affected per the CVE)
  4. Verify Win32K subsystem presence
    Confirm the system runs a full GUI Windows desktop (not Server Core) by checking if the Win32K.sys driver exists: `dir C:\Windows\System32\drivers\win32k.sys`
    Affected if The system has the Win32K.sys driver present, which is standard for all desktop Windows and non-Server Core installations - this is the component with the vulnerability

The system is affected if it runs any of the listed Windows 10 or 11 versions with a build number below the fixed threshold, or if it is Windows Server 2012 R2, and the Win32K graphics subsystem is present (standard desktop Windows installations).

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 updates for this vulnerability as soon as they become available through Windows Update or the Microsoft Security Update Guide. Organizations should prioritize patching endpoints given the high-severity rating and local privilege escalation capability.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2026-57095 from Windows Update or the Microsoft Update Catalog to reach the fixed build number for your specific Windows version

  1. Check the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify which Windows version and build number is installed from the affected list (Windows 10 1607, 1809, 21h2, 22h2, Windows 11 24h2, 25h2, 26h1, or Windows Server 2012/R2)
  3. Apply the Microsoft security update for CVE-2026-57095 from the Microsoft Security Response Center (msrc.microsoft.com) corresponding to your Windows version
  4. Restart the system after applying the update
  5. Verify the build number matches or exceeds the fixed version: 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
Caveat Standard Windows cumulative update risks apply (potential for compatibility issues with legacy software; test in non-production environment first)

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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