Local information disclosure via Win32K buffer over-read
Published Aug 11, 2026 · Updated Aug 25, 2026
Buffer over-read in Microsoft Windows Win32K allows local users to disclose protected memory through locally executed code. Win32K reads beyond the end of a buffer and exposes adjacent memory to a low-privileged process; Microsoft has not identified the affected function or input path. A low-privileged account and local code execution are required, and the documented consequence is confidentiality loss without integrity or availability impact.
Summary
What happened
Buffer over-read in Microsoft Windows Win32K allows local users to disclose protected memory through locally executed code. Win32K reads beyond the end of a buffer and exposes adjacent memory to a low-privileged process; Microsoft has not identified the affected function or input path. A low-privileged account and local code execution are required, and the documented consequence is confidentiality loss without integrity or availability impact.
The record
- CVE
- CVE-2026-62746
- Published
- Aug 11, 2026
- Updated
- Aug 25, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-126
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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.17763.0 <10.0.17763.9121
What conditions does exploitation require?
What is affected?
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