On this page (7 sections)
CVE-2026-95962 is a use-after-free vulnerability in the Windows Virtual Filtering Platform (VFP). According to the NVD record, it allows an unauthorized attacker to execute code over a network. The record was published on 2026-11-10 and carries a CVSS score of 9 with a critical severity rating.
If you administer Windows servers, hosts that run virtualization or software-defined networking, or hosting infrastructure built on Windows, this is worth tracking today. The public information is still very short, so this article separates what is confirmed from what is not yet known.
What is confirmed so far
The only primary source in hand is the NVD entry, which gives a one-sentence description: a use after free in Windows VFP that lets an unauthorized attacker execute code over a network. The record lists one reference, the Microsoft Security Response Center page CVE-2026-95962 in the MSRC update guide. The research does not include the contents of that page.
Only one independent publisher covers this story so far, and the sources provided do not contain details beyond the description. In particular, the following are not confirmed in the material available:
- Which Windows and Windows Server versions are affected
- Which update fixes the issue, or its KB number
- Whether the flaw is being exploited, or whether public proof-of-concept code exists
- The CVSS vector, such as whether user interaction or specific privileges are needed
- Whether any workaround or mitigation exists
Check the MSRC page listed in the NVD record for any vendor guidance, and compare whatever it says with the Windows builds you run.
What a use-after-free in VFP means
A use after free (CWE-416) happens when a program releases a block of memory but keeps a pointer to it, then later uses that pointer. If an attacker can influence what gets placed in that freed memory, the program may read or run data the attacker controls. In the worst case this leads to code execution, which is what the description claims here.
The Virtual Filtering Platform is a Windows networking component. It is generally described as the packet-processing layer behind virtual switching and software-defined networking features, such as those used with Hyper-V. That background is general knowledge and is not spelled out in the CVE record, so confirm how VFP is used in your own environment rather than assuming from this paragraph.
The phrase "over a network" in the description suggests the vulnerable code can be reached by network traffic. The exact conditions, for example which interfaces or traffic must be reachable, are not described in the available sources.
Who is realistically exposed
Until affected products are confirmed, the safest assumption is that systems using Windows virtual networking features deserve priority. That includes:
- Hyper-V hosts and virtual switches
- Windows Server systems that provide software-defined networking
- Hosting and private cloud setups built on Windows virtualization
- Developer and test machines with Hyper-V or container networking enabled
A standard Windows desktop or a web server that does not use virtualization features may be less exposed, but that is an inference, not a confirmed statement. Do not rule systems out until an affected-product list is available and you have compared it with your builds.
How to check your exposure
Start by building an inventory of Windows systems and noting which ones use Hyper-V or virtual switching. The first command below lists the installed Windows build, so you can compare it with any affected builds once they are published. Run it in PowerShell on each system; it is read-only.
Get-ComputerInfo -Property WindowsProductName, WindowsVersion, OsBuildNumberThe next command lists the Hyper-V virtual switches on a host, which tells you whether the virtual networking layer is in use. Run it in an elevated PowerShell session on a Hyper-V host. If the Hyper-V module is not installed, the command will report that, which is itself useful information.
Get-VMSwitchTo see which updates are already installed, so you can later confirm that a fixing update is present, use the following. It prints the 15 most recently installed updates.
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 15What to do now
- Open the MSRC page for CVE-2026-95962 and note any affected products and fixing update it lists for each Windows version you run.
- Inventory Windows hosts, and flag those running Hyper-V, virtual switches or software-defined networking.
- Check Windows Update, WSUS or your patch tool for a fixing update, and test it on a non-critical host first.
- Deploy the update to flagged hosts first, then to the rest of your Windows fleet, following your normal change process.
- Restrict network access to management and virtualization hosts so only trusted networks can reach them.
- Confirm after patching that the update shows in the installed updates list and that virtual machines and networking still work.
- Watch for any later update to this record, such as an exploitation status change or a mitigation.
Detection and monitoring
The sources do not describe indicators of compromise or any known exploitation, so there is no specific signature to hunt for. Reasonable general steps are to review host crash and restart events on virtualization servers, watch for unexpected new processes or services on hosts, and keep an eye on unusual inbound traffic to management networks.
For a broader view of your public-facing systems, a read-only scan of your verified sites with Webforta Scan can help you spot exposed services and outdated software, though it cannot confirm whether an internal Windows component like VFP is patched. For general guidance on spotting compromise, see how to check if a website is hacked.
Keep patching routine
Single-CVE alerts like this one are easier to handle when you already have a regular patch rhythm and a current inventory. For a practical baseline, see our guide to website security for small business.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
