Remote code execution via kernel heap overflow
Published Sep 8, 2026 · Updated Sep 9, 2026
Heap-based buffer overflow in the Windows Kernel allows remote attackers to execute code through network-delivered input. Microsoft identifies heap memory corruption but has not disclosed the affected kernel routine, protocol, or mis-sized operation on untrusted data. Exploitation requires no credentials but does require user interaction, and successful exploitation executes code in the affected security context.
Summary
What happened
Heap-based buffer overflow in the Windows Kernel allows remote attackers to execute code through network-delivered input. Microsoft identifies heap memory corruption but has not disclosed the affected kernel routine, protocol, or mis-sized operation on untrusted data. Exploitation requires no credentials but does require user interaction, and successful exploitation executes code in the affected security context.
The record
- CVE
- CVE-2026-69669
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 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.17763.0 <10.0.17763.9245
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.
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