dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50432

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 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
Use after free in Windows Virtual Filtering Platform (VFP) allows an authorized attacker to deny service over a 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 Use After Free (UAF) vulnerability exists in Windows Virtual Filtering Platform (VFP), a kernel-mode filtering engine used in Windows Server and hypervisor environments. The flaw allows an authorized attacker to trigger a denial of service condition over a network by exploiting improper memory management in VFP's handling of network traffic filtering operations.

MitigationApply Microsoft security updates for Windows when available. In the interim, restrict authorized access to the network segments where VFP is active and monitor for anomalous traffic patterns indicative of DoS attempts.

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.2269< 10.0.28000.2525
Windows Server 2016Operating system
Affected:< 10.0.14393.9339

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

CVSS:3.1/AV:N/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. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows version and build number
    Affected if The version/build falls below any of these thresholds: 10.0.14393.9339, 10.0.17763.9020, 10.0.19044.7548, 10.0.19045.7548, 10.0.26100.8875, 10.0.26200.8875, 10.0.28000.2269, or 10.0.28000.2525
  2. Verify if Virtual Filtering Platform is enabled
    Check for VFP service status via 'Get-Service VFP' in PowerShell, or look for VFP.sys driver loaded via 'driverquery /v | findstr VFP'
    Affected if The VFP service is running or the VFP.sys driver is loaded in memory
  3. Confirm hypervisor role is installed
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' or check if Hyper-V is present via 'systeminfo' under Hyper-V Requirements
    Affected if Hyper-V or other virtualization roles that leverage VFP are installed and active
  4. Identify network filtering configurations using VFP
    Check for VFP extension or filtering components via 'Get-NetAdapter' and review any NDIS filters or VFP extension logs in event viewer under 'Microsoft-Windows-VFP/Debug'
    Affected if Network filtering extensions or VFP-powered virtual switches are configured (such as Hyper-V virtual switches)
  5. Review crash dumps for UAF indicators
    Examine Windows Memory Dumps or Kernel Dumps in %SystemRoot%\Minidump for evidence of VFP-related memory corruption, or check System event logs for Event ID 1001 (Bugcheck) referencing VFP
    Affected if Recent crash dumps show VFP.sys involved in a use-after-free fault or memory corruption

A system is affected if it runs any Windows version within the affected build ranges AND has Virtual Filtering Platform (VFP) enabled through Hyper-V or network filtering roles.

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
Interim mitigation

Apply Microsoft security updates for Windows when available. In the interim, restrict authorized access to the network segments where VFP is active and monitor for anomalous traffic patterns indicative of DoS attempts.

Recommended fix High confidence

Microsoft Security Update (see KB numbers per Windows version in steps)

  1. Identify the Windows version and build number by running 'winver' or 'systeminfo'
  2. Navigate to Microsoft Update Catalog or Windows Update settings
  3. Search for and install the applicable Microsoft security update for this vulnerability
  4. For Windows 10 1607/Server 2016: Install KB5055527 (build 10.0.14393.9339)
  5. For Windows 10 1809: Install KB5055537 (build 10.0.17763.9020)
  6. For Windows 10 21h2: Install KB5055494 (build 10.0.19044.7548)
  7. For Windows 10 22h2: Install KB5055525 (build 10.0.19045.7548)
  8. For Windows 11 24h2: Install KB5055533 (build 10.0.26100.8875)

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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