Remote code execution via LLTD heap overflow
Published Sep 8, 2026 · Updated Sep 10, 2026
Heap-based buffer overflow in Microsoft Windows LLTD allows remote attackers to execute code through crafted network traffic. Microsoft identifies heap memory corruption in the LLTD protocol handler but has not published the affected routine or malformed field that causes the overwrite. Exploitation requires no credentials or user interaction, but high-complexity conditions and access to the target's network link; success runs attacker-controlled code on the target.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows LLTD allows remote attackers to execute code through crafted network traffic. Microsoft identifies heap memory corruption in the LLTD protocol handler but has not published the affected routine or malformed field that causes the overwrite. Exploitation requires no credentials or user interaction, but high-complexity conditions and access to the target's network link; success runs attacker-controlled code on the target.
The record
- CVE
- CVE-2026-69732
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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