dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-47973

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 →
81/100
Remediation priority · High
No privileges

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
Buffer over-read in Virtual Hard Disk (VHDX) allows an unauthorized 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 buffer over-read vulnerability exists in the VHDX virtual hard disk parsing logic. When a specially crafted VHDX file is processed, the code reads beyond the allocated buffer boundary, allowing a local attacker to read sensitive memory contents and leverage this for local privilege escalation.

MitigationApply vendor patches for VHDX-handling software immediately. Until patched, restrict access to VHDX file handling to trusted users only and monitor for unauthorized VHDX file placement.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' and compare the full build number to the affected ranges: 10.0.10240.21073 (1507), 10.0.14393.8246 (1607), 10.0.17763.7558 (1809), 10.0.19044.6093 (21h2), 10.0.19045.6093 (22h2), 10.0.22621.5624 (22h2), 10.0.22631.5624 (23h2), 10.0.26100.4652 (24h2). Versions below these thresholds are affected.
    Affected if The installed Windows build number is less than the corresponding threshold for your Windows version and feature update.
  2. Identify Hyper-V role status
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell or check via 'Control Panel > Programs and Features > Turn Windows features on or off' to see if Hyper-V is enabled.
    Affected if Hyper-V is enabled and the Windows version is vulnerable, as VHDX files are primarily processed by Hyper-V components.
  3. Check for VHDX-related services
    Run 'Get-Service | Where-Object {$_.DisplayName -like "*Virtual*Hard*" -or $_.DisplayName -like "*Hyper-V*"}' to list services related to virtual disk handling.
    Affected if VHDX-handling services (such as Hyper-V Virtual Machine Management) are running on a vulnerable Windows version.

You are affected if the Windows build number falls below the specified thresholds for your specific Windows version and feature update, especially when VHDX-handling components like Hyper-V are 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 vendor patches for VHDX-handling software immediately. Until patched, restrict access to VHDX file handling to trusted users only and monitor for unauthorized VHDX file placement.

Recommended fix High confidence

Upgrade to the latest available Windows 10 or Windows 11 release for your hardware (Windows 10 22h2 build 19045+ or Windows 11 24h2 build 26100+)

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 release channel the system is on (1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, or 24h2)
  3. Open Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to download and install the latest security updates
  5. Verify the installed build number matches or exceeds the fixed version for your release: 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.26100.4652
  6. If automatic updates do not reach the required version, download and install the relevant Cumulative Update from the Microsoft Update Catalog manually
Caveat Standard Windows update risks apply; ensure critical data is backed up before applying updates

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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