dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49730

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Time-of-check time-of-use (toctou) race condition in Microsoft Windows QoS scheduler allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A time-of-check time-of-use (TOCTOU) race condition in the Microsoft Windows QoS (Quality of Service) scheduler allows a locally authorized attacker to exploit the timing window between checking a condition and using the resource, potentially elevating privileges to SYSTEM level.

MitigationApply the relevant Microsoft Windows security update for CVE-2025-49730 through standard Windows Update or patch management processes; prioritize workstations and servers with sensitive data or external attack exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' or 'Get-ComputerInfo WindowsVersion,OsBuildNumber' in PowerShell
    Affected if The build number is lower than any of the following: 10240.21073 (1507), 14393.8246 (1607), 17763.7558 (1809), 19044.6093 (21h2/22h2), 22621.5624 (11 22h2), 22631.5624 (11 23h2), or 26100.4652 (11 24h2)
  2. Confirm exact OS edition
    Run 'systeminfo' or 'Get-ComputerInfo CsName,OsName,OsVersion,OsBuildNumber' to get the full OS name and build
    Affected if The displayed build number falls below the threshold for your specific Windows 10 or Windows 11 release
  3. Identify QoS scheduler component
    Check for the presence of QoS-related services: run 'sc query QoS' or review 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\QoS' in registry
    Affected if The QoS scheduler service exists on the system (this is the component with the vulnerability)

The system is affected if it runs any Windows 10 or 11 version with a build number lower than the thresholds listed and has the QoS scheduler component present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply the relevant Microsoft Windows security update for CVE-2025-49730 through standard Windows Update or patch management processes; prioritize workstations and servers with sensitive data or external attack exposure.

Recommended fix High confidence

Upgrade to the fixed versions: Windows 10 1507: 10.0.10240.21073+, Windows 10 1607: 10.0.14393.8246+, Windows 10 1809: 10.0.17763.7558+, Windows 10 21h2: 10.0.19044.6093+, Windows 10 22h2: 10.0.19045.6093+, Windows 11 22h2: 10.0.22621.5624+, Windows 11 23h2: 10.0.22631.5624+, Windows 11 24h2: 10.0.2

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Settings > Update & Security > Windows Update, or use WSUS/SCCM for enterprise deployments
  3. Install all pending Windows updates, which will include the security patch for this vulnerability
  4. Alternatively, download the specific security update from Microsoft Update Catalog based on your Windows version (KB reference available on msrc.microsoft.com)
  5. After installation, restart the system when prompted
  6. Verify the update was applied by checking 'winver' to confirm the version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update - no breaking changes expected; this is a security patch, not a feature change

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49730 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49730 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data