dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-45593

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.17763.8880 / 10.0.19044.7417 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Use after free in Windows SDK allows an authorized attacker to elevate privileges locally.

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

Use after free vulnerability in Windows SDK that allows a local authorized attacker to elevate privileges. This memory corruption flaw occurs when memory is accessed after being freed, potentially enabling arbitrary code execution with higher privileges.

MitigationApply Microsoft security updates for Windows SDK when released; limit local system access to essential trusted personnel only; monitor for indicators of local privilege escalation attempts.

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.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2019Operating system
Affected:< 10.0.17763.8880

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 if Windows SDK is installed
    Open Registry Editor and navigate to HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots, or check for the presence of C:\Program Files (x86)\Windows Kits\10\bin directory
    Affected if The Windows SDK is not installed on the system - the vulnerability only applies if the SDK is present
  2. Find the installed Windows SDK version
    In the registry under HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots, look for the 'KitsRoot10' value and then check the version folder under the bin directory, or run 'reg query "HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots"' from command prompt
    Affected if Cannot determine the SDK version - the exact installed version must be identified to compare against affected ranges
  3. Compare installed SDK version to affected ranges
    Match the installed SDK build number (e.g., 10.0.17763.xxxx format) against the vulnerable ranges: Windows 10 1809/Server 2019 < 10.0.17763.8880, Windows 10 21h2 < 10.0.19044.7417, Windows 10 22h2 < 10.0.19045.7417, Windows 11 23h2 < 10.0.22631.7219, Windows 11 24h2 < 10.0.26100.8655, Windows 11 25h2 < 10.0.26200.8655, Windows 11 26h1 < 10.0.28000.2269
    Affected if The installed version number is lower than any of the threshold versions listed for the corresponding Windows release
  4. Verify the vulnerable feature is in use
    This is a Use After Free in the Windows SDK - the vulnerability is triggerable when specific SDK components are used by an application. Check if any custom or third-party applications on the system utilize the Windows SDK, particularly in contexts where low-level memory operations occur
    Affected if Applications or services that leverage the Windows SDK for affected operations are running on the system

A user is affected if the Windows SDK is installed and its version falls below the patched build numbers for the corresponding Windows release, and the system runs applications or code paths that exercise the vulnerable SDK component.

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.8880 / 10.0.19044.7417 / 10.0.19045.7417 or later
Fixed in 10.0.17763.888010.0.19044.741710.0.19045.7417
Interim mitigation

Apply Microsoft security updates for Windows SDK when released; limit local system access to essential trusted personnel only; monitor for indicators of local privilege escalation attempts.

Recommended fix Moderate confidence

Install the Microsoft security update corresponding to CVE-2026-45593 from Windows Update or the Microsoft Update Catalog

  1. Open Windows Settings and navigate to Windows Update
  2. Check for and install the latest Windows security updates
  3. Verify the installed build version matches or exceeds the fixed version for your Windows edition: Windows 10 1809: build 17763.8880 or higher | Windows 10 21h2: build 19044.7417 or higher | Windows 10 22h2: build 19045.7417 or higher | Windows 11 23h2: build 22631.7219 or higher | Windows 11 24h2: build 26100.8655 or higher | Windows 11 25h2: build 26200.8655 or higher | Windows 11 26h1: build 280
  4. Restart the system after applying the update
  5. Confirm the installed KB patch addresses the Windows SDK vulnerability
Caveat Standard Windows update - minimal risk; ensure backups of critical data before applying

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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