CVE-2025-48822
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 · uneditedOut-of-bounds read in Windows Hyper-V allows an unauthorized 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 confidenceAn out-of-bounds read vulnerability exists in Windows Hyper-V's virtualization infrastructure. The memory safety flaw allows an unauthorized local attacker to read beyond allocated memory boundaries, which can be leveraged to achieve arbitrary code execution at the hypervisor level.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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 installedRun 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell or check Programs and Features for Hyper-V componentsAffected if The Hyper-V feature is enabled or installed on the system
-
Confirm Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the exact Windows build numberAffected if The installed Windows build number falls below the fixed version for the corresponding release (e.g., below 10.0.14393.8246 for Windows 10 1607/Server 2016, below 10.0.17763.7558 for Windows 10 1809, etc.)
-
Check Hyper-V virtualization infrastructure componentInspect the Hyper-V hypervisor component via 'Get-VMHypervisor' in PowerShell or verify hvix.exe/hvax.exe version in System32 (if present)Affected if The hypervisor binaries are present and the Windows version is within the affected ranges
A system is affected if Hyper-V is enabled and the Windows build number is lower than the fixed version for that specific Windows release branch.
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 Microsoft security updates for Windows Hyper-V when released. As a compensating control, restrict local access to hypervisor hosts and implement network segmentation to limit the attack surface.
Install the relevant cumulative security update for your Windows version (e.g., KB number from the monthly security patch cycle containing the CVE-2025-48822 fix)
- Open Settings on the affected Windows system
- Navigate to Windows Update (Update & Security > Windows Update)
- Click 'Check for updates' to retrieve the latest available patches
- Locate and install the cumulative security update that includes the fix for CVE-2025-48822
- Restart the system if prompted to complete the installation
- Verify the installed update by checking the Windows Update history - the installed KB should contain the fix for this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48822 — 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-48822 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