Microsoft has patched a serious vulnerability in Windows’ Virtualization-Based Security (VBS) enclaves that could allow a local attacker to steal sensitive information and use it to compromise an entire host. Tracked as CVE-2026-20935, the flaw is classified as an information disclosure but carries outsized risk because the leaked data—encryption keys, memory addresses, and attestation secrets—can act as a stepping stone to full system control.

What Happened with CVE-2026-20935

VBS enclaves are supposed to be digital fortresses: isolated regions of memory where even the Windows kernel can’t tread. They protect your most sensitive assets, from encryption keys to authentication tokens. CVE-2026-20935 pokes a hole in that isolation. An attacker with local, authorized access can exploit a path in the enclave or its supporting attestation services to read data that should remain sealed.

Microsoft’s advisory is deliberately vague on the technical details—a common practice to slow down exploit development. But the update guide confirms the vulnerability exists in the VBS enclave component and affects all supported Windows versions with VBS enabled. The company has released patches through its standard channels, and the fix is included in the latest cumulative updates. Because specific KB numbers vary by Windows edition and build, administrators must consult the Microsoft Security Update Guide for the correct package.

The attack requires a toehold on the target machine, but that bar is low in many environments. A malicious virtual machine on a shared Hyper-V host could trigger the flaw through storage or integration channels. A compromised admin workstation or a rogue insider with low privileges could invoke vulnerable enclave APIs. Even a remote attack that first gains a foothold on a guest VM could pivot to the host using this leak as part of a chain.

Why a Small Leak Is a Big Deal

Information disclosure bugs are often downplayed, but in the context of a security boundary like VBS, they are force multipliers. Even a few leaked bytes can:

  • Defeat kernel protections: Memory addresses hidden by Kernel Address Space Layout Randomization (KASLR) become visible, making kernel exploits reliable.
  • Compromise attestation: Leaked attestation artifacts or keys let attackers forge health certificates, bypassing security checks.
  • Accelerate exploitation: A leak reduces the time and sophistication needed to turn a limited foothold into SYSTEM-level code execution.

Security researchers have long warned that VBS enclave bugs are especially dangerous because they erode the trust model underpinning Windows’ most advanced defenses—Credential Guard, Hypervisor-enforced Code Integrity (HVCI), and Secure Launch. A successful enclave information leak doesn’t just expose data; it undermines the assumptions that the rest of your security stack relies on.

Who Needs to Worry

Home Users and Small Businesses

If you’ve enabled Memory Integrity or Credential Guard on your Windows 10 or 11 PC, your system uses VBS and is technically affected. However, the real-world risk for standalone users is lower unless you regularly run untrusted virtual machines or provide remote access to your machine. Still, you should apply the update when it arrives through Windows Update.

IT Administrators and Enterprises

This is where the risk concentrates. Prioritize these systems:

  • Hyper-V hosts with VBS enabled, especially in multi-tenant or shared environments.
  • Management jump boxes and servers that interact with enclaves or attestation services.
  • Virtual Desktop Infrastructure (VDI) hosts and cluster nodes.
  • Any endpoint with Credential Guard, HVCI/Memory Integrity, or Secure Launch activated.

If you don’t know which machines have VBS on, now is the time to inventory. Use msinfo32.exe (look for the “Virtualization-based security” row) or run this PowerShell command as admin:

Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard

Tag every system where the output shows VBS is active—they need the patch first.

Developers

Applications that rely on VBS enclaves for attestation, key storage, or secure computation should be considered vulnerable until the host is patched. Verify that your build and test environments receive the update, and re-evaluate any security assumptions your software makes about enclave confidentiality.

How We Got Here

VBS isn’t new. Microsoft introduced it with Windows 10 and Server 2016 as a way to protect secrets from the kernel itself—a response to waves of kernel-mode malware. Over the years, features like Credential Guard and Application Guard have depended on VBS to keep credentials and browser sessions locked down.

But isolation is hard. The same complexity that keeps attackers out can introduce subtle bugs. This isn’t the first VBS enclave vulnerability, and it won’t be the last. As virtualization-based security has become more widespread, so has researcher attention. A string of previous CVEs—some of them taking advantage of improper input validation in enclave interfaces—has shown that the trust boundary between the normal Windows world and the secure world is a high-value target.

Microsoft has generally been responsive, fixing reported issues within Patch Tuesday cycles and sometimes providing out-of-band updates. The company’s advisory process, however, intentionally omits deep exploit mechanics. That helps prevent mass exploitation in the window between disclosure and patching but leaves defenders without clear indicators of compromise. The burden of detection falls on behavioral telemetry and anomaly hunting.

Immediate Steps to Protect Your Systems

1. Patch Immediately (or Apply Compensating Controls)

  • Find your KB: Open the Microsoft Security Update Guide for CVE-2026-20935, expand the list of affected products, and note the KB number matching your Windows version and build.
  • Validate in the Update Catalog: Search for that KB in the Microsoft Update Catalog to confirm the exact package before deploying.
  • Pilot first: Deploy to a representative set of machines that includes Hyper-V hosts, management servers, and clustered nodes. Test live migration, attestation, and backup workflows before a broader rollout.
  • Stage rollouts: After pilot success, push updates in waves: management hosts first, then hypervisors, domain controllers, and finally endpoints.

If you can’t patch immediately, implement these short-term mitigations:

  • Restrict which user accounts can mount or attach VHD/VHDX files.
  • Limit enclave provisioning privileges to a small set of trusted administrators.
  • Enforce Just-in-Time (JIT) admin access and network segmentation for management interfaces.
  • Enable Memory Integrity (HVCI) and strict driver-signing policies via Group Policy or WDAC.

2. Hunt for Signs of Exploitation

Without vendor-supplied indicators, you must rely on behavioral detection:

  • Monitor DeviceIoControl calls: Look for unusual or frequent IOCTL requests targeting virtualization service providers from non-privileged processes. Your EDR should flag these.
  • Track process ancestry: Alert on any unexpected process spawning with NT AUTHORITY\SYSTEM rights from a low-privilege lineage.
  • Watch enclave activity: Log and alert on enclave provisioning, attestation, or re-provisioning events from accounts that shouldn’t be performing them.
  • Investigate kernel crashes: If you see BSODs referencing storvsp.sys or enclave components, preserve full memory dumps and minidumps for analysis.

Centralize Windows Event Logs for service crashes, process creation, and device attach/detach events. Use canary or sandboxed workflows to establish a baseline of normal enclave behavior before tuning detection rules.

3. Prepare Forensically

If you suspect a host has been compromised:

  • Isolate the machine from the network but do not reboot it—memory artifacts are critical.
  • Capture a full memory image and any Windows Error Reporting (WER) minidumps before shutting down.
  • Preserve logs for IOCTL sequences and enclave events; these can help vendors reconstruct attack chains.

Long-Term Hardening and Outlook

Patching CVE-2026-20935 closes a door, but the neighborhood remains active. VBS enclaves will continue to attract scrutiny because they sit at the intersection of the most privileged code on a Windows system. Microsoft is likely to keep hardening these boundaries, and future Windows releases may introduce additional sandboxing for enclave interfaces.

For defenders, this means making baseline hardening a habit:

  • Enforce least privilege everywhere; revoke enclave provisioning rights from all but a handful of admins.
  • Use Windows Defender Application Control (WDAC) or AppLocker to restrict what runs on management and hypervisor hosts.
  • Segment live-migration and storage networks from tenant-facing networks.
  • Maintain driver blocklists and enforce strict driver signing.

Keep an eye on the Microsoft Security Response Center for any updates to this advisory. Often, additional technical details or revised risk assessments appear as more information becomes available. While no public exploit code has been reported at the time of writing, the post-patch window tends to see a spike in reverse-engineering activity. Assume that determined attackers are analyzing the fix and plan accordingly.

CVE-2026-20935 is a reminder that even “just an information disclosure” can be the linchpin of a sophisticated attack. Patch now, hunt actively, and harden the virtual foundations that modern Windows security depends on.