dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-50167

HIGH · 7.0 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.10240.21100 / 10.0.14393.8330 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Hyper-V 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 race condition vulnerability in Windows Hyper-V involves improper synchronization when accessing shared resources, allowing an authorized local attacker to exploit the timing window and elevate privileges to a higher level on the host system.

MitigationApply Microsoft security updates for Hyper-V when released; restrict local access to Hyper-V hosts to trusted, authorized users only.

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.21100
Windows 10 1607Operating system
Affected:< 10.0.14393.8330
Windows 10 1809Operating system
Affected:< 10.0.17763.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 version against affected ranges
    Run 'winver' or 'systeminfo' and note the full Windows build number (e.g., 10.0.19045.6216 for Windows 10 22h2). Compare your build to the listed thresholds: 10.0.10240.21100 (1507), 10.0.14393.8330 (1607), 10.0.17763.7678 (1809), 10.0.19044.6216 (21h2), 10.0.19045.6216 (22h2), 10.0.22621.5768 (11 22h2), 10.0.22631.5768 (11 23h2), 10.0.26100.4851 (11 24h2).
    Affected if Your Windows build number is LOWER than the corresponding threshold for your Windows version.
  2. Verify Hyper-V is installed
    Open PowerShell and run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All | Select-Object State' or check 'systeminfo' output for 'Hyper-V Requirements' status.
    Affected if Hyper-V is installed and the State shows 'Enabled' or systeminfo reports Hyper-V as present.
  3. Confirm Hyper-V Hypervisor is running
    Run 'bcdedit /enum all' and look for 'hypervisorlaunchtype' under Windows Boot Loader, or run 'msinfo32' and check the 'Hyper-V - Hypervisor' line.
    Affected if The hypervisorlaunchtype is set to 'Auto' or msinfo32 shows 'Yes' for the hypervisor, indicating Hyper-V is actively running.

You are affected if your Windows version is below the listed threshold AND Hyper-V is installed and running on your system.

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.21100 / 10.0.14393.8330 / 10.0.17763.7678 or later
Fixed in 10.0.10240.2110010.0.14393.833010.0.17763.7678
Interim mitigation

Apply Microsoft security updates for Hyper-V when released; restrict local access to Hyper-V hosts to trusted, authorized users only.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21100 or later | Windows 10 1607: 10.0.14393.8330 or later | Windows 10 1809: 10.0.17763.7678 or later | Windows 10 21h2: 10.0.19044.6216 or later | Windows 10 22h2: 10.0.19045.6216 or later | Windows 11 22h2: 10.0.22621.5768 or later | Windows 11 23h2: 10.0.22631.5768 or

  1. Identify current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Compare the installed build number against the fixed version for your Windows release
  3. For Windows 10: Ensure Windows Update is enabled and run 'Check for updates' to install KB5055527 or subsequent security updates
  4. For Windows 11: Run Windows Update and install KB5055527 or subsequent security updates
  5. Alternatively, download the specific security update from the Microsoft Update Catalog for your Windows version and architecture
  6. After installation, restart the system to apply the Hyper-V privilege elevation patch
  7. Verify the patch installed correctly by checking the installed updates list or running 'winver' to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows security update with no expected breaking changes; as a privilege elevation fix, ensure appropriate testing on critical systems before deployment

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50167 — 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-50167 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