Local privilege escalation via driver type confusion
Published Jun 9, 2026 · Updated Jun 9, 2026
Type confusion in Microsoft Windows Kernel-Mode Drivers allows local users with low privileges to elevate privileges on affected systems. A kernel-mode driver accesses a resource through an incompatible type, but Microsoft has not disclosed the driver, code path, or attacker-controlled input. Low-privilege local code execution is required, and Microsoft describes the outcome only as elevated privileges without naming the resulting security context.
Summary
What happened
Type confusion in Microsoft Windows Kernel-Mode Drivers allows local users with low privileges to elevate privileges on affected systems. A kernel-mode driver accesses a resource through an incompatible type, but Microsoft has not disclosed the driver, code path, or attacker-controlled input. Low-privilege local code execution is required, and Microsoft describes the outcome only as elevated privileges without naming the resulting security context.
The record
- CVE
- CVE-2026-45600
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2025 (Server Core installation)
- Classifications
- CWE-843, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.26100.0 <10.0.26100.32995
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo