CVE-2025-24048
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 · uneditedHeap-based buffer overflow in Role: 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 · high confidenceHeap-based buffer overflow vulnerability in Windows Hyper-V allows a locally authorized attacker to corrupt heap memory and elevate privileges to higher permission levels. The vulnerability stems from insufficient bounds checking in Hyper-V's role components, enabling memory corruption that can be exploited for local privilege escalation.
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.7876< 10.0.17763.7009< 10.0.19044.5608< 10.0.19045.5608< 10.0.22621.5039< 10.0.26100.3403> 10.0.26100.3403, < 10.0.26100.3476< 10.0.14393.7876< 10.0.17763.7009CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Hyper-V is installedRun 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All' in PowerShell and check if State is 'Enabled', or run 'Get-VM' to see if any VMs exist (indicating Hyper-V is active)Affected if Hyper-V is installed and enabled, then the system could be affected if the Windows version is vulnerable
-
Confirm Windows version matches affected rangesRun 'winver' or 'systeminfo | findstr /B /C:"OS"' to get the exact build number. Compare against: Windows 10 1607 (build < 14393.7876), 1809 (build < 17763.7009), 21h2 (build < 19044.5608), 22h2 (build < 19045.5608); Windows 11 22h2 (build < 22621.5039), 24h2 (build < 26100.3403 or between 3403 and 3476); Windows Server 2016 (build < 14393.7876), 2019 (build < 17763.7009)Affected if Your installed build number falls below the fixed version for your specific Windows release
-
Check Hyper-V role components are presentOn Windows Server, run 'Get-WindowsFeature -Name *Hyper-V*' and verify Hyper-V role is installed. On Windows 10/11, verify the Hyper-V Windows optional feature is enabled via 'Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*Hyper-V*"}'Affected if The Hyper-V role or feature is installed, exposing the vulnerable bounds-checking code in role components
-
Confirm attacker has local accessReview local user permissions and account status. The vulnerability requires a locally authorized attacker, so check for standard user or privileged accounts present on the systemAffected if There are local user accounts on the system (the vulnerability can be exploited by any locally authorized user)
-
Verify current patch stateCheck installed updates for KB5002537 or subsequent Hyper-V related patches, or run 'Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10' to see recent security updatesAffected if No security update containing the CVE-2025-24048 fix has been installed, leaving the unpatched version in use
You are affected if Hyper-V is installed on a Windows version within the affected build ranges and the CVE-2025-24048 security update has not been applied.
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.787610.0.17763.700910.0.19044.5608
Apply Microsoft security updates for CVE-2025-24048 through Windows Update or WSUS. For production Hyper-V environments, test patches in a staging environment before deploying during a planned maintenance window to ensure VM availability is not impacted.
Windows 10 1607: build 10.0.14393.7876 | Windows 10 1809: build 10.0.17763.7009 | Windows 10 21h2: build 10.0.19044.5608 | Windows 10 22h2: build 10.0.19045.5608 | Windows 11 22h2: build 10.0.22621.5039 | Windows 11 24h2: build 10.0.26100.3476 | Windows Server 2016: build 10.0.14393.7876 | Windows S
- 1. Identify the current Windows build version by running `winver` or `systeminfo` in Command Prompt
- 2. Determine which Windows version and build you are running (e.g., Windows 10 22h2, Windows 11 24h2, Windows Server 2019)
- 3. Open Windows Settings and navigate to Windows Update, or check Microsoft Update Catalog at catalog.update.microsoft.com
- 4. Search for and install the appropriate Windows security update for your version that includes the fix for CVE-2025-24048
- 5. For Windows 10 1607: install update reaching build 10.0.14393.7876 or later
- 6. For Windows 10 1809: install update reaching build 10.0.17763.7009 or later
- 7. For Windows 10 21h2: install update reaching build 10.0.19044.5608 or later
- 8. For Windows 10 22h2: install update reaching build 10.0.19045.5608 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24048 — 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-24048 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