CVE-2025-49730: CVE-2025-49730: Time-of-check time-of-use (toctou) race condition in Microsoft Windows QoS scheduler allow…
microsoft · windows 10 1507 · NVD published 2025-07-08 · posted 2025-08-11 · last modified 2026-06-17
What it is
Time-of-check time-of-use (toctou) race condition in Microsoft Windows QoS scheduler allows an authorized attacker to elevate privileges locally.
| Weakness | CWE-122CWE-367 |
|---|---|
| CVSS vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (source: [email protected]) |
| ATT&CK tactics | Execution |
Exploitation evidence
First exploit evidence seen: 2025-08-11 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
Exploit-DB
- EDB-52399: Microsoft Windows - Storage QoS Filter Driver Checker (2025-08-11)
Sources: Exploit-DB (OffSec).
Defend the Chain
The attack chain for CVE-2025-49730 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.
Pick a red technique card on the board, then choose the defence that stops it.
Defend against T1203 Exploitation for Client Execution Inferred
Inferred from CWE CWE-122
How to fix it
Fixed versions
- microsoft windows 10 1507: upgrade to 10.0.10240.21073 or later
- microsoft windows 10 1607: upgrade to 10.0.14393.8246 or later
- microsoft windows 10 1809: upgrade to 10.0.17763.7558 or later
- microsoft windows 10 21h2: upgrade to 10.0.19044.6093 or later
- microsoft windows 10 22h2: upgrade to 10.0.19045.6093 or later
- microsoft windows 11 22h2: upgrade to 10.0.22621.5624 or later
- microsoft windows 11 23h2: upgrade to 10.0.22631.5624 or later
- microsoft windows 11 24h2: upgrade to 10.0.26100.4652 or later
- microsoft windows server 2016: upgrade to 10.0.14393.8246 or later
- microsoft windows server 2019: upgrade to 10.0.17763.7558 or later
- microsoft windows server 2022: upgrade to 10.0.20348.3932 or later
- microsoft windows server 2022 23h2: upgrade to 10.0.25398.1732 or later
- microsoft windows server 2025: upgrade to 10.0.26100.4652 or later
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-49730 (Vendor Advisory)
MITRE ATT&CK mitigations for this chain
- M1050 Exploit Protection (for T1203) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
- M1051 Update Software (for T1203) : Perform regular software updates to mitigate exploitation risk. Keeping software up-to-date with the latest security patches helps prevent adversaries from exploiting known vulnerabilities in client software, reducing the risk of successful attacks.
- M1048 Application Isolation and Sandboxing (for T1203) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. Risks of additional exploits and weaknesses in those systems may still exist.
Detection Generic guidance
- Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.