Local privilege escalation via TCP/IP race condition
Published Sep 8, 2026 · Updated Sep 10, 2026
A race condition in Windows TCP/IP across affected Windows releases allows local users with low privileges to elevate privileges. Microsoft identifies improper synchronization of a shared resource during concurrent execution but has not disclosed the specific TCP/IP code path or resource involved. Exploitation requires local access, low privileges, no user interaction, and winning a high-complexity race; success grants elevated privileges with broad system impact.
Summary
What happened
A race condition in Windows TCP/IP across affected Windows releases allows local users with low privileges to elevate privileges. Microsoft identifies improper synchronization of a shared resource during concurrent execution but has not disclosed the specific TCP/IP code path or resource involved. Exploitation requires local access, low privileges, no user interaction, and winning a high-complexity race; success grants elevated privileges with broad system impact.
The record
- CVE
- CVE-2026-69404
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
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.
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