dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2026-47652

HIGH · 8.2 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.20348.5256 / 10.0.22631.7219 or later.
See remediation →
84/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
Heap-based buffer overflow 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 confidence

Heap-based buffer overflow vulnerability in Windows Hyper-V hypervisor allowing an authorized local attacker to execute arbitrary code. The vulnerability resides in the hypervisor's memory management and enables privilege escalation from a guest VM to the host system.

MitigationApply Microsoft security updates for Windows Hyper-V once released. Prioritize patching Hyper-V hosts in production environments given the high CVSS score and local privilege escalation vector.

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 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2022Operating system
Affected:< 10.0.20348.5256
Windows Server 2025Operating system
Affected:< 10.0.26100.32995

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Hyper-V role is enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' or check in Programs and Features > Windows Features. Alternatively, run 'systeminfo' and look for Hyper-V in the list.
    Affected if Hyper-V is installed and the status shows Enabled or the feature is listed as present
  2. Check Windows build version
    Run 'winver' or 'systeminfo' and note the OS Name and OS Version/Build Number. For PowerShell, run '[System.Environment]::OSVersion.Version' or 'Get-ComputerInfo | Select-Object OsBuildNumber,OsVersion'
    Affected if The build number matches any of the affected versions listed (23h2, 24h2, 25h2, 26h1, Server 2022, or Server 2025) and is below the fixed build numbers
  3. Compare against affected version ranges
    Match your detected build number to these thresholds: Windows 11 23h2 < 10.0.22631.7219, Windows 11 24h2 < 10.0.26100.8655, Windows 11 25h2 < 10.0.26200.8655, Windows 11 26h1 < 10.0.28000.2269, Windows Server 2022 < 10.0.20348.5256, Windows Server 2025 < 10.0.26100.32995
    Affected if Your installed Windows build number falls below the corresponding threshold for your Windows version and Hyper-V is enabled

You are affected if Hyper-V is enabled and your Windows build version is lower than the fixed version for your specific Windows release.

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.20348.5256 / 10.0.22631.7219 / 10.0.26100.8655 or later
Fixed in 10.0.20348.525610.0.22631.721910.0.26100.8655
Interim mitigation

Apply Microsoft security updates for Windows Hyper-V once released. Prioritize patching Hyper-V hosts in production environments given the high CVSS score and local privilege escalation vector.

Recommended fix High confidence

Install KB updates to reach: Windows 11 23h2 >= 10.0.22631.7219 | Windows 11 24h2 >= 10.0.26100.8655 | Windows 11 25h2 >= 10.0.26200.8655 | Windows 11 26h1 >= 10.0.28000.2269 | Windows Server 2022 >= 10.0.20348.5256 | Windows Server 2025 >= 10.0.26100.32995

  1. Open Windows Settings and navigate to Windows Update
  2. Check for updates and install all available security updates
  3. Alternatively, manually download and install the specific KB patch from Microsoft Update Catalog corresponding to your Windows version
  4. Restart the system after installing updates
  5. Verify the build version matches or exceeds the fixed version for your Windows release (e.g., 10.0.22631.7219 for Windows 11 23h2)
Caveat Standard Windows update risks - ensure backups and test in non-production environments before rolling out broadly

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

Fix this in Windows 11 23h2 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-2026-47652 — 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-2026-47652 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