CVE-2025-48807
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 · uneditedImproper restriction of communication channel to intended endpoints in Windows Hyper-V allows an authorized attacker to execute code 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 confidenceThis is a Windows Hyper-V vulnerability involving improper restriction of communication channels to intended endpoints. An authorized attacker with local access can exploit this flaw to execute code within the hypervisor context, potentially escaping the boundaries of their virtual machine or escalating privileges on the host system.
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< 10.0.14393.8246< 10.0.17763.7558< 10.0.19044.6093< 10.0.19045.6093< 10.0.22621.5624< 10.0.22631.5624< 10.0.26100.4652< 10.0.14393.8246CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Hyper-V is enabled on the systemRun 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All' in PowerShell, or check via 'Get-HyperV -ComputerName localhost' if Hyper-V PowerShell module is installedAffected if The Hyper-V feature shows as Enabled - this means the system is a potential hypervisor host and may be affected
-
Obtain the installed Windows version and build numberRun 'winver' from command prompt, or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in command prompt, or run '[System.Environment]::OSVersion.Version' in PowerShellAffected if The build number is below the specific threshold for your Windows release (see version list)
-
Get precise build number for version comparisonRun 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v UBR' to get the full build (CurrentBuild.UBR)Affected if The full build number (CurrentBuild.UBR) is less than the threshold for your Windows version (e.g., for Windows 10 22h2, less than 19045.6093)
-
Confirm the Windows release name for accurate comparisonRun 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v DisplayVersion' to get the release name (e.g., 21H2, 22H2)Affected if The release matches any of the affected versions listed in the CVE (10 1607, 10 1809, 10 21h2, 10 22h2, 11 22h2, 11 23h2, 11 24h2, or Server 2016)
-
Identify if this is a Hyper-V host serverRun 'Get-WindowsFeature -Name *Hyper-V*' on Windows Server, or check if the system serves VMs, or review 'vmcompute' service status via 'Get-Service vmcompute'Affected if The system has the Hyper-V server role installed or is running Hyper-V to host virtual machines
You are affected if Hyper-V is enabled and your Windows build number is below the threshold for your specific Windows release (e.g., less than 19045.6093 for Windows 10 22h2, or less than 10.0.26100.4652 for Windows 11 24h2).
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.824610.0.17763.755810.0.19044.6093
Apply the relevant Microsoft security update for Windows Hyper-V once released. Prioritize patching Hyper-V hosts in production environments and verify VM functionality after deployment.
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 | Windows Server 2016: 10.0.14393.8246
- Open Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest cumulative update
- For Windows Server 2016, use Windows Server Update Services (WSUS) or manually download the update from the Microsoft Update Catalog
- Restart the system after installing the update
- Verify the installed update by running 'winver' and confirming the build number matches or exceeds the fixed version for your Windows edition
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-48807 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48807 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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