dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54091

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
Integer overflow or wraparound 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

An integer overflow or wraparound vulnerability exists in Windows Hyper-V that allows a locally authorized attacker to elevate their privileges. The vulnerability stems from improper integer handling within the Hyper-V hypervisor component, potentially allowing an attacker with local access to exploit the overflow and gain higher-level system privileges.

MitigationApply the Microsoft security update for CVE-2025-54091 to all affected Windows Hyper-V hosts. Ensure Hyper-V virtualization infrastructure is fully patched as part of regular security maintenance cycles.

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. Check Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full version and build number.
    Affected if The installed Windows version and build number fall within the affected ranges: Windows 10 1507 < 10.0.10240.21128, Windows 10 1607 < 10.0.14393.8422, Windows 10 1809 < 10.0.17763.7792, Windows 10 21h2 < 10.0.19044.6332, Windows 10 22h2 < 10.0.19045.6332, Windows 11 22h2 < 10.0.22621.5909, Windows 1
  2. Verify Hyper-V is enabled
    Open PowerShell and run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' to check if the Hyper-V feature is installed and enabled, or check via Programs and Features > Turn Windows features on or off for Hyper-V.
    Affected if Hyper-V is installed and enabled on the system, making it a potential Hyper-V host.
  3. Confirm Hyper-V hypervisor component presence
    Open Command Prompt and run 'systeminfo' or 'msinfo32' and look for Hyper-V entries in the firmware or software sections, or run 'bcdedit /enum all' to check for hypervisor launch options.
    Affected if The Hyper-V hypervisor is present and loaded on the system, indicating this is a Hyper-V host that could be vulnerable.

A system is affected if it runs an unpatched Windows version within the affected build ranges AND has Hyper-V enabled or is configured as a Hyper-V host.

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 the Microsoft security update for CVE-2025-54091 to all affected Windows Hyper-V hosts. Ensure Hyper-V virtualization infrastructure is fully patched as part of regular security maintenance cycles.

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. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine the Windows release (e.g., 10 1507, 10 1607, 10 1809, 10 21h2, 10 22h2, 11 22h2, 11 23h2, 11 24h2)
  3. Open Windows Update: Start > Settings > Update & Security > Windows Update
  4. Click 'Check for updates' and install all available updates
  5. Alternatively, manually download and install the appropriate Cumulative Update for your Windows version from the Microsoft Update Catalog
  6. Verify the installed version meets or exceeds the fixed threshold for your release
Caveat Standard Windows update; review release notes for any known compatibility issues before deploying in production environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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