dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50485

MEDIUM · 5.7 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
59/100
Remediation priority · Elevated
Zero-click Patch available 5 weeks old

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
Buffer over-read in Windows Hyper-V allows an authorized attacker to deny service over an adjacent network.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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 buffer over-read vulnerability exists in Windows Hyper-V that allows an authorized attacker on an adjacent network to cause a denial of service. The flaw involves reading beyond the boundaries of allocated memory buffers, potentially triggering a crash or unstable state in the hypervisor.

MitigationApply Microsoft security updates for Windows Hyper-V when released. Review and harden adjacent network access controls to limit exposure to potential attackers.

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.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2525
Windows Server 2012Operating system
Affected:all versions= 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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/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 is enabled
    Open PowerShell as Administrator and run: Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All | Select-Object State
    Affected if State is 'Enabled' - the vulnerability only applies when Hyper-V is installed and running
  2. Determine Windows 10 build number
    Run 'winver' from Run dialog or 'systeminfo' in Command Prompt; note the full OS Build number (e.g., 10.0.19045.7548)
    Affected if For Windows 10 1607: build < 10.0.14393.9339; 1809: build < 10.0.17763.9020; 21h2: build < 10.0.19044.7548; 22h2: build < 10.0.19045.7548
  3. Determine Windows 11 build number
    Run 'winver' or 'systeminfo'; note the full OS Build number
    Affected if For Windows 11 24h2: build < 10.0.26100.8875; 25h2: build < 10.0.26200.8875; 26h1: build < 10.0.28000.2525
  4. Check Windows Server version
    Run 'winver' or check System Properties to identify Windows Server 2012 or 2012 R2
    Affected if Any Windows Server 2012 or Windows Server 2012 R2 installation with Hyper-V enabled is affected regardless of build

System is affected if Hyper-V is enabled and the installed Windows build number is lower than the fixed version for that specific Windows release, or if running Windows Server 2012/R2 with Hyper-V.

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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply Microsoft security updates for Windows Hyper-V when released. Review and harden adjacent network access controls to limit exposure to potential attackers.

Recommended fix High confidence

Upgrade to the fixed build for your Windows release: Windows 10 1607 to build 10.0.14393.9339+, Windows 10 1809 to build 10.0.17763.9020+, Windows 10 21h2 to build 10.0.19044.7548+, Windows 10 22h2 to build 10.0.19045.7548+, Windows 11 24h2 to build 10.0.26100.8875+, Windows 11 25h2 to build 10.0.26

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 release branch you are on (e.g., 1607, 1809, 21h2, 22h2, 24h2, 25h2, 26h1)
  3. For Windows 10: Navigate to Settings > Update & Security > Windows Update and check for updates, or manually download the appropriate cumulative update from the Microsoft Update Catalog for your specific build (e.g., KB5055528 for build 19045)
  4. For Windows 11: Navigate to Settings > Windows Update and check for updates, ensuring you receive the specific build that meets or exceeds the fixed version for your release
  5. For Windows Server 2012 R2: Since this version is end-of-life with no security updates, migrate to a supported Windows Server version (e.g., Windows Server 2022) and rebuild the Hyper-V host
  6. After updating, verify the installed build number matches or exceeds the fixed version for your release branch
Caveat Windows Server 2012 R2 is end-of-life with no security patches available - migration to a newer Windows Server version is required; ensure Hyper-V VMs are compatible with the new Windows version before upgrading

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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