CVE-2026-69830
Awaiting Analysis
Awaiting Analysis - Queue
Race Condition in Windows DHCP Server
Vulnerability report for CVE-2026-69830, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2026-10-13
Last updated on: 2026-10-13
Assigner: Microsoft Corporation
Description
Description
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows DHCP Server allows an unauthorized attacker to execute code over a network.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| Microsoft | Windows | 10 Version 1607 10.0.14393.0 |
| Microsoft | Windows | 10 Version 1809 10.0.17763.0 |
| Microsoft | Windows | Server 2012 6.2.9200.0 |
| Microsoft | Windows | Server 2012 (Server Core installation) 6.2.9200.0 |
| Microsoft | Windows | Server 2012 R2 6.3.9600.0 |
| Microsoft | Windows | Server 2012 R2 (Server Core installation) 6.3.9600.0 |
| Microsoft | Windows | Server 2016 10.0.14393.0 |
| Microsoft | Windows | Server 2016 (Server Core installation) 10.0.14393.0 |
| Microsoft | Windows | Server 2019 10.0.17763.0 |
| Microsoft | Windows | Server 2019 (Server Core installation) 10.0.17763.0 |
| Microsoft | Windows | Server 2022 10.0.20348.0 |
| Microsoft | Windows | Server 2025 10.0.26100.0 |
| Microsoft | Windows | Server 2025 (Server Core installation) 10.0.26100.0 |
Helpful Resources
Exploitability
CWE
KEV
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
