dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-54092

HIGH · 7.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.17763.7792 / 10.0.19044.6332 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
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 exists in Windows Hyper-V's shared resource synchronization mechanism. An authorized local attacker can exploit improper synchronization during concurrent execution to escalate privileges to a higher integrity level.

MitigationApply Microsoft security updates for Hyper-V when released. Prioritize patching on systems running Hyper-V with local authorized users. Follow least-privilege principles to limit local user permissions.

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 1809Operating system
Affected:< 10.0.17763.7792
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909
Windows 11 24h2Operating system
Affected:< 10.0.26100.6508
Windows Server 2019Operating system
Affected:< 10.0.17763.7792
Windows Server 2022Operating system
Affected:< 10.0.20348.4106

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 if Hyper-V is enabled on the system
    Open PowerShell as Administrator and run: Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All | Select-Object -Property State
    Affected if The State shows 'Enabled' - if disabled, the system is not vulnerable to this specific Hyper-V flaw
  2. Check the installed Windows version
    Run 'winver' from Run dialog, or in PowerShell run: [System.Environment]::OSVersion.Version.ToString()
    Affected if The version is lower than any of these: 10.0.17763.7792, 10.0.19044.6332, 10.0.19045.6332, 10.0.22621.5909, 10.0.22631.5909, 10.0.26100.6508, 10.0.20348.4106 (match your build number to the corresponding product version list)
  3. Confirm the exact build number for precise version matching
    Run 'systeminfo' in Command Prompt and look at the OS Version line, or in PowerShell run: Get-ComputerInfo | Select-Object -ExpandProperty OsVersion
    Affected if The build number (fourth segment after Windows 10/11) is lower than the thresholds in the affected version list for your Windows release

You are affected only if Hyper-V is enabled AND your Windows build number falls below the version thresholds listed for your specific Windows product and release.

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.17763.7792 / 10.0.19044.6332 / 10.0.19045.6332 or later
Fixed in 10.0.17763.779210.0.19044.633210.0.19045.6332
Interim mitigation

Apply Microsoft security updates for Hyper-V when released. Prioritize patching on systems running Hyper-V with local authorized users. Follow least-privilege principles to limit local user permissions.

Recommended fix High confidence

Upgrade to the minimum fixed build for your Windows version: Windows 10 1809 (build 17763.7792+), Windows 10 21h2 (build 19044.6332+), Windows 10 22h2 (build 19045.6332+), Windows 11 22h2 (build 22621.5909+), Windows 11 23h2 (build 22631.5909+), Windows 11 24h2 (build 26100.6508+), Windows Server 20

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows product and version is installed (e.g., Windows 10 22h2, Windows 11 23h2, Windows Server 2022)
  3. 3. Compare the current build number against the fixed version for that product: Windows 10 1809 requires build 10.0.17763.7792 or higher; Windows 10 21h2 requires build 10.0.19044.6332 or higher; Windows 10 22h2 requires build 10.0.19045.6332 or higher; Windows 11 22h2 requires build 10.0.22621.5909 or higher; Windows 11 23h2 requires build 10.0.22631.5909 or higher; Windows 11 24h2 requires build
  4. 4. If the current build is below the required fixed version, apply the latest Windows Security Update (KB) from Microsoft Update Catalog that corresponds to the CVE-2025-54092 patch, or upgrade to a newer Windows version that includes the fix
  5. 5. After patching, restart the system as required
  6. 6. Verify the fix was applied by checking the installed updates or running 'winver' to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows update risks apply - ensure backups and test in non-production environment first; some updates may require restart

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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