dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-47999

MEDIUM · 6.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.14393.8246 / 10.0.17763.7558 or later.
See remediation →
70/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
Missing synchronization in Windows Hyper-V allows an authorized attacker to deny service over an adjacent 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

A missing synchronization (race condition) vulnerability in Windows Hyper-V allows an authenticated attacker on an adjacent network to cause a denial of service. The flaw stems from improper synchronization handling in the hypervisor's network components, potentially leading to resource exhaustion or unexpected termination of virtual machines or the host.

MitigationApply the relevant Microsoft security patches for Windows Hyper-V as soon as they become available through standard Windows Update channels. Prioritize patching in environments where Hyper-V hosts are accessible from adjacent network segments.

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.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652
Windows Server 2016Operating system
Affected:< 10.0.14393.8246

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

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/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. Confirm Hyper-V is installed
    Run 'systeminfo' and look for 'Hyper-V' in the OS Name or run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell
    Affected if Hyper-V is listed as installed or the feature state shows it is enabled
  2. Check Windows version against affected ranges
    Run 'winver' or 'systeminfo' and note the full build number (e.g., 10.0.19045.XXXX)
    Affected if The installed Windows build number is lower than any of these: 14393.8246 (Win10 1607/Server 2016), 17763.7558 (Win10 1809), 19044.6093 (Win10 21h2), 19045.6093 (Win10 22h2), 22621.5624 (Win11 22h2), 22631.5624 (Win11 23h2), or 26100.4652 (Win11 24h2)
  3. Verify Hyper-V virtual switch exists
    Run 'Get-VMSwitch' in PowerShell or check Hyper-V Virtual Switch Manager
    Affected if A virtual switch is configured, as the vulnerability is in hypervisor network components
  4. Confirm network accessibility from adjacent network
    Review network adapter bindings and firewall rules for Hyper-V virtual switches (typically vEthernet adapters)
    Affected if Hyper-V virtual switches are exposed to adjacent network segments without network segmentation or additional filtering

The system is affected if Hyper-V is installed, the Windows build is below the fixed versions listed, and Hyper-V virtual switches are active on the host.

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.8246 / 10.0.17763.7558 / 10.0.19044.6093 or later
Fixed in 10.0.14393.824610.0.17763.755810.0.19044.6093
Interim mitigation

Apply the relevant Microsoft security patches for Windows Hyper-V as soon as they become available through standard Windows Update channels. Prioritize patching in environments where Hyper-V hosts are accessible from adjacent network segments.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8246 | Windows 10 1809: 10.0.17763.7558 | Windows 10 21h2: 10.0.19044.6093 | Windows 10 22h2: 10.0.19045.6093 | Windows 11 22h2: 10.0.22621.5624 | Windows 11 23h2: 10.0.22631.5624 | Windows 11 24h2: 10.0.26100.4652 | Windows Server 2016: 10.0.14393.8246

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine the build number (e.g., 10.0.14393.xxxx) from the version information
  3. Navigate to Windows Update: Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to download and install the latest security updates
  5. Alternatively, manually download the specific KB update from Microsoft Update Catalog matching your Windows version
  6. Restart the system after updates are installed
  7. Verify the fix by running 'winver' to confirm the build number matches or exceeds the fixed version for your release
Caveat Standard Windows security update; no breaking changes expected for this denial-of-service patch

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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