dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2026-25170

HIGH · 7.0 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.20348.4830 / 10.0.22631.6783 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Use after free in 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 · moderate confidence

A use-after-free vulnerability exists in Windows Hyper-V, Microsoft's virtualization platform. This memory corruption flaw allows an authorized local attacker to exploit freed memory and achieve privilege escalation, potentially gaining elevated system or administrative access.

MitigationApply Microsoft security updates for Windows Hyper-V as soon as they become available. Limit local access to Hyper-V hosts and follow least-privilege principles to reduce attack surface.

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.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719
Windows Server 2022Operating system
Affected:< 10.0.20348.4830
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.2207
Windows Server 2025Operating system
Affected:< 10.0.26100.32463

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

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

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

  1. Verify Hyper-V role is installed
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell and check the State property, or run 'systeminfo' and look for Hyper-V in the OS Configuration list
    Affected if Hyper-V is installed and enabled (State = Enabled)
  2. Determine Windows build number
    Run 'winver' or execute 'Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber' in PowerShell. Note the full build number including the revision (last 4 digits)
    Affected if Build number is below the threshold for the corresponding Windows version
  3. Confirm affected version range
    Cross-reference your Windows version and full build number against the affected version list: Windows 11 23h2 (< 10.0.22631.6783), 24h2 (< 10.0.26100.7979), 25h2 (< 10.0.26200.7979), 26h1 (< 10.0.28000.1719), Server 2022 (< 10.0.20348.4830), Server 2022 23h2 (< 10.0.25398.2207), Server 2025 (< 10.0.26100.32463)
    Affected if Your installed version falls below the specified threshold for your Windows edition
  4. Identify if host is a Hyper-V server
    Run 'Get-VMHost -ComputerName localhost' in PowerShell (requires Hyper-V PowerShell module). If the command succeeds, this system is a Hyper-V host
    Affected if The system is configured as a Hyper-V host and meets the vulnerable version criteria

You are affected if Hyper-V is enabled and your Windows build number is below the threshold for your specific Windows version or edition.

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.4830 / 10.0.22631.6783 / 10.0.25398.2207 or later
Fixed in 10.0.20348.483010.0.22631.678310.0.25398.2207
Interim mitigation

Apply Microsoft security updates for Windows Hyper-V as soon as they become available. Limit local access to Hyper-V hosts and follow least-privilege principles to reduce attack surface.

Recommended fix High confidence

Windows 11 23h2: build 10.0.22631.6783+ | Windows 11 24h2: build 10.0.26100.7979+ | Windows 11 25h2: build 10.0.26200.7979+ | Windows 11 26h1: build 10.0.28000.1719+ | Windows Server 2022: build 10.0.20348.4830+ | Windows Server 2022 23h2: build 10.0.25398.2207+ | Windows Server 2025: build 10.0.261

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which affected product and version you are running from the list: Windows 11 23h2/24h2/25h2/26h1, Windows Server 2022, Windows Server 2022 23h2, or Windows Server 2025
  3. Apply the latest Windows Security Update (KB) from Microsoft Update Catalog that addresses this vulnerability
  4. For Windows 11 23h2: upgrade to build 10.0.22631.6783 or later
  5. For Windows 11 24h2: upgrade to build 10.0.26100.7979 or later
  6. For Windows 11 25h2: upgrade to build 10.0.26200.7979 or later
  7. For Windows 11 26h1: upgrade to build 10.0.28000.1719 or later
  8. For Windows Server 2022: upgrade to build 10.0.20348.4830 or later
Caveat Standard Windows security updates typically do not introduce breaking changes; verify application compatibility after applying

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

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