Microsoft · Windows · Microsoft Windows Race Condition Vulnerability
Verdict
Patch on your normal cycle · actively exploited, not reachable unauthenticated from the internet, and in the top 10% of CVEs by near-term exploitation probability
Added to CISA KEV 2025-11-12 · exploited in the wild for 319 days
CVSS 7.0 HIGH. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.
| Attack vector | localrequires local access to the machine |
|---|---|
| Privileges required | lowneeds some credentials, so a fully anonymous attacker cannot reach it directly |
| User interaction | nonecan be triggered with nobody interacting with the page or request |
| Base vector | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Weakness | CWE-362 |
This describes the vulnerability. It says nothing about whether your systems run it.
EPSS puts the probability of exploitation in the next 30 days at 0.0599, which places it in the top 10% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.
| EPSS probability | 0.0599 |
|---|---|
| Percentile | 0.931 — top 10% |
| Added to KEV | 2025-11-12 |
|---|---|
| Days exploited | 319 |
| Federal remediation due | not set |
| Ransomware use | no known ransomware campaign use |
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.