dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62567

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.14393.8688 / 10.0.17763.8146 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
Integer underflow (wrap or wraparound) in Windows Hyper-V allows an authorized attacker to deny service over a network.

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

This is an integer underflow vulnerability in Windows Hyper-V's network stack that can be exploited remotely by an authorized attacker to cause a denial of service condition. The integer wraparound allows malformed network inputs to crash the Hyper-V virtualization platform, potentially affecting all VMs running on affected hosts.

MitigationApply Microsoft security updates for Windows Server with Hyper-V role when released. Isolate Hyper-V hosts behind network segmentation and restrict administrative access to trusted personnel only until patches are available.

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 10 1607Operating system
Affected:< 10.0.14393.8688
Windows 10 1809Operating system
Affected:< 10.0.17763.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2012Operating system
Affected:= r2

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/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 enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell, or check in Server Manager under Hyper-V role
    Affected if Hyper-V is installed and the role is enabled - the vulnerability only affects systems with Hyper-V running
  2. Check installed Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build number
    Affected if The build number falls below the fixed versions: 14393.8688 (1607), 17763.8146 (1809), 19044.6691 (21h2), 19045.6691 (22h2), 22631.6345 (23h2), 26100.7392 (24h2), 26200.7392 (25h2), or is Windows Server 2012 R2
  3. Confirm Hyper-V virtual switches exist
    Run 'Get-VMSwitch -SwitchType External' in Hyper-V PowerShell module to list external virtual switches
    Affected if External virtual switches are configured - the network stack vulnerability is triggered via malformed network inputs to virtual switches

The system is affected if Hyper-V is enabled and the Windows build version is lower than the fixed versions for the respective Windows release, or if running Windows Server 2012 R2 with Hyper-V role.

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.14393.8688 / 10.0.17763.8146 / 10.0.19044.6691 or later
Fixed in 10.0.14393.868810.0.17763.814610.0.19044.6691
Interim mitigation

Apply Microsoft security updates for Windows Server with Hyper-V role when released. Isolate Hyper-V hosts behind network segmentation and restrict administrative access to trusted personnel only until patches are available.

Recommended fix High confidence

Upgrade to the fixed build version for your Windows version (see version numbers in steps); for Windows Server 2012 R2 apply KB5063025 or later security update

  1. Verify current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify which Windows version and build you are running from the affected list
  3. Apply the latest Windows Security Update from Microsoft Update Catalog or Windows Update
  4. Restart the system after installing the update
  5. Verify the update was successful by checking the build version matches or exceeds: Windows 10 1607: 10.0.14393.8688, Windows 10 1809: 10.0.17763.8146, Windows 10 21h2: 10.0.19044.6691, Windows 10 22h2: 10.0.19045.6691, Windows 11 23h2: 10.0.22631.6345, Windows 11 24h2: 10.0.26100.7392, Windows 11 25h2: 10.0.26200.7392, or for Windows Server 2012 R2 apply the corresponding KB5063025 or later securi
Caveat Standard Windows update - review release notes for any known issues before deployment in production environments

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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