Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged local access
  2. Delivery
    Invoke vulnerable SDK component
  3. Exploit
    Trigger integer overflow causing use-after-free
  4. Execution
    Groom heap to control freed object
  5. Persist
    Hijack execution in privileged context
  6. Impact
    Escalate to SYSTEM

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must already have local code execution as a low-privileged authenticated user on a Windows host that has the vulnerable Windows SDK component installed or loaded (PR:L, AV:L, UI:N). No user interaction is required, but exploitation is limited to scenarios where the attacker can invoke or feed input to a process linked against the affected SDK runtime - typically developer workstations, build servers, or systems with SDK redistributable components present. Remote, unauthenticated exploitation is not possible per the CVSS vector, and kiosked or hardened endpoints without local code execution avenues are not realistically exposed.

Impact

The CVSS vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates a local attacker with low privileges and no user interaction can fully compromise confidentiality, integrity, and availability - a classic local privilege escalation profile scored 7.8 (High). There is a notable inconsistency between the CWE classification (CWE-190 Integer Overflow) and the description (use-after-free), and the tags also include 'Denial Of Service' which is inconsistent with the C:H/I:H/A:H impact metrics - defenders should verify the exact root cause with Microsoft's advisory before relying on detections. EPSS data is not provided in the input, the vulnerability is not listed in CISA KEV, and no POC has been identified, so real-world exploitation risk should be treated as moderate: high impact if chained with initial access, but not currently a mass-exploitation priority. Because the SDK is a developer-side component, exposure is concentrated on workstations and build hosts rather than production servers, narrowing the realistic attack surface.

Exploit ScenarioDerived

A low-privileged user - for example, a standard domain account on a developer workstation or a CI build agent - executes a crafted local binary or input file that triggers the use-after-free in an SDK-provided component. The attacker grooms the heap so that the freed object is replaced with attacker-controlled data, then forces a dereference that hijacks execution and runs code at SYSTEM or another high-privileged context, completing local privilege escalation.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 09, 2026

Local privilege escalation in Microsoft Windows SDK enables an authenticated low-privileged attacker to elevate to higher privileges by exploiting a use-after-free memory corruption flaw. The CVSS 7.8 (AV:L/AC:L/PR:L) profile reflects local attack with low complexity and low privileges required, yielding full confidentiality, integrity, and availability impact. No public exploit identified at time of analysis and the vulnerability is not currently listed in CISA KEV.

RemediationAI

Patch availability per vendor advisory should be confirmed by reviewing the Microsoft Security Response Center entry at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45593 and applying the fixed Windows SDK release once Microsoft publishes the exact build numbers; the input data does not include a specific patched version. As compensating controls until patches are deployed, restrict local interactive and RDP access on developer workstations and build agents to trusted users, enforce least-privilege on accounts that run SDK tooling, and monitor for unexpected child processes or token manipulation by SDK-linked binaries - note that tightening local access can disrupt developer productivity and CI pipelines, so coordinate with engineering teams. Application allowlisting (e.g., Windows Defender Application Control) can further reduce the risk of arbitrary local binaries triggering the vulnerable code path at the cost of additional rule maintenance.

Affected VersionsENISA

Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7417
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8880
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8880
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7219
Windows Server 2022 10.0.20348.0 <10.0.20348.5256
Windows Server 2019 10.0.17763.0 <10.0.17763.8880
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8655
Windows Server 2025 10.0.26100.0 <10.0.26100.32995
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32995
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7417
Windows 11 version 26H1 1.0.0 <10.0.28000.2269
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8655

Affected Packages

microsoft windows_10_version_1809_10_0_17763_8880 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.8880, Windows 10 Version 1809 for x64-based Systems 10.0.17763.8880
microsoft windows_10_version_21h2_10_0_19044_7417 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7417, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7417, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7417
microsoft windows_10_version_22h2_10_0_19045_7417 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7417, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7417, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7417
microsoft windows_11_version_23h2_10_0_22631_7219 fix: Windows 11 Version 23H2 for ARM64-based Systems 10.0.22631.7219, Windows 11 Version 23H2 for x64-based Systems 10.0.22631.7219
microsoft windows_11_version_24h2_10_0_26100_8655 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8655, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655
microsoft windows_11_version_25h2_10_0_26200_8655 fix: Windows 11 Version 25H2 for ARM64-based Systems 10.0.26200.8655, Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655
microsoft windows_11_version_26h1_10_0_28000_2269 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2269
microsoft windows_11_version_26h1_extra_10_0_28000_2269 fix: Windows 11 Version 26H1 for x64-based Systems - extra 10.0.28000.2269
microsoft windows_server_2019_10_0_17763_8880 fix: Windows Server 2019 10.0.17763.8880, Windows Server 2019 (Server Core installation) 10.0.17763.8880
microsoft windows_server_2022_10_0_20348_5256 fix: Windows Server 2022 10.0.20348.5256, Windows Server 2022 (Server Core installation) 10.0.20348.5256
microsoft windows_server_2025_10_0_26100_32995 fix: Windows Server 2025 10.0.26100.32995, Windows Server 2025 (Server Core installation) 10.0.26100.32995
euvd windows_10_version_1809 fix: 10.0.17763.8880
euvd windows_10_version_21h2 fix: 10.0.19044.7417
euvd windows_10_version_22h2 fix: 10.0.19045.7417
euvd windows_11_version_23h2 fix: 10.0.22631.7219
euvd windows_11_version_24h2 fix: 10.0.26100.8655
euvd windows_11_version_25h2 fix: 10.0.26200.8655
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2019 fix: 10.0.17763.8880
euvd windows_server_2019_server_core_installation fix: 10.0.17763.8880
euvd windows_server_2022 fix: 10.0.20348.5256
euvd windows_server_2025 fix: 10.0.26100.32995
euvd windows_server_2025_server_core_installation fix: 10.0.26100.32995

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 23 packages in microsoft, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw resides in the Microsoft Windows SDK, the developer toolkit that ships headers, libraries, and runtime components used to build Windows applications. Although the CWE is tagged as CWE-190 (Integer Overflow), the description identifies a use-after-free condition, suggesting an integer overflow that miscomputes an allocation size or reference count and leads to premature freeing of an object that is later dereferenced. Exploiting such a dangling pointer typically yields control over a freed heap chunk, allowing an attacker to corrupt adjacent structures or hijack object virtual tables to achieve code execution in the context of a higher-privileged process linked against the SDK runtime.

Know when Windows 10 1809 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CIRCL (temporal) 6.8 MEDIUM

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Use after free in Windows SDK allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

Microsoft Windows SDK contains a local privilege escalation vulnerability (CVE-2026-45593) that allows authenticated low-privilege users to gain full system access through memory corruption. The absence of a vendor patch creates persistent risk for organizations relying on Windows SDK in development or build environments. Without active exploitation observed to date, the vulnerability remains a significant insider threat and lateral movement vector if systems are compromised.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Enforce role-based access controls limiting SDK access to authorized developers; (2) Run SDK components with minimal required privileges; (3) Monitor kernel-level privileged transitions and memory access violations on systems running SDK; (4) Implement application whitelisting for SDK binaries to prevent tampering; (5) Segment development systems running SDK from critical infrastructure to limit lateral movement if exploited.

Threat Intelligence Overview

EPSS Score
0.1%
Top 76% exploitable
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2021-1732 HIGH POC
7.8 Feb 25

Windows Win32k contains an out-of-bounds write vulnerability enabling local privilege escalation to SYSTEM, exploited by

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2021-36934 HIGH POC
7.8 Jul 22

Windows contains an elevation of privilege vulnerability known as 'HiveNightmare' or 'SeriousSAM' where overly permissiv

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2024-21412 HIGH POC
8.1 Feb 13

Internet Shortcut Files Security Feature Bypass Vulnerability. Rated high severity (CVSS 8.1), this vulnerability is rem

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy