dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54098

HIGH · 7.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.10240.21128 / 10.0.14393.8422 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
Improper access control 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

Improper access control in Windows Hyper-V allows an authenticated attacker with local access to escalate privileges, potentially gaining administrator or SYSTEM-level access on the host or guest VMs.

MitigationApply Microsoft security updates for Windows Hyper-V when available; review and restrict Hyper-V administrator permissions to least-privilege principles.

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.21128
Windows 10 1607Operating system
Affected:< 10.0.14393.8422
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

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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the installed Windows version and build number
    Affected if The build number falls below any of these thresholds: 10.0.10240.21128 (Win10 1507), 10.0.14393.8422 (Win10 1607), 10.0.17763.7792 (Win10 1809), 10.0.19044.6332 (Win10 21h2), 10.0.19045.6332 (Win10 22h2), 10.0.22621.5909 (Win11 22h2), 10.0.22631.5909 (Win11 23h2), 10.0.26100.6508 (Win11 24h2)
  2. Verify Hyper-V is installed
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All' in PowerShell or check 'Programs and Features' for Hyper-V components
    Affected if Hyper-V is present and enabled on the system
  3. Confirm Hyper-V services are running
    Run 'Get-Service | Where-Object {$_.Name -like "*vm*" -or $_.Name -like "*hyper*"}' to list VM-related services, check for 'vmcompute', 'vmms', 'vmwp' services status
    Affected if Any Hyper-V virtual machine management services are in a Running state
  4. Check for local user access
    Review which users have local access to the system using 'Get-LocalUser' or 'net user' commands. This vulnerability requires an authenticated attacker with local access.
    Affected if The system has user accounts beyond the built-in administrator that could provide an attacker local access foothold

Your environment is affected if you are running any of the listed Windows versions with Hyper-V enabled and services running, particularly if non-privileged local users exist on the 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.21128 / 10.0.14393.8422 / 10.0.17763.7792 or later
Fixed in 10.0.10240.2112810.0.14393.842210.0.17763.7792
Interim mitigation

Apply Microsoft security updates for Windows Hyper-V when available; review and restrict Hyper-V administrator permissions to least-privilege principles.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21128 or later | Windows 10 1607: 10.0.14393.8422 or later | Windows 10 1809: 10.0.17763.7792 or later | Windows 10 21h2: 10.0.19044.6332 or later | Windows 10 22h2: 10.0.19045.6332 or later | Windows 11 22h2: 10.0.22621.5909 or later | Windows 11 23h2: 10.0.22631.5909 or

  1. Open Windows Update settings on the affected Windows system
  2. Check for and install the latest Windows security updates (KB references can be found at msrc.microsoft.com for CVE-2025-54098)
  3. Restart the system after applying the update
  4. Verify the update was installed successfully by checking Windows Update history
Caveat Standard Windows security update - no breaking changes expected for this privilege escalation patch

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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