Microsoft disclosed a sensitive information disclosure flaw in the Windows Container Isolation FS Filter Driver, unionfs.sys, on July 14, 2026. Tracked as CVE-2026-50428, the vulnerability affects Windows 11 version 26H1 and allows a locally authenticated attacker with low privileges to read memory that should be inaccessible. The fix is available now in cumulative update KB5101649, which advances the OS to build 28000.2525.
The Flaw: An Out-of-Bounds Read in a Container Driver
unionfs.sys is a file-system filter driver that enables the union mount technology critical to Windows container isolation. It layers multiple storage views into a single logical file system, a design widely used for container images and their writable layers. The bug is an out-of-bounds read (CWE-125): when processing certain operations, the driver can access memory beyond the intended region, potentially exposing data from kernel memory.
Microsoft rated the vulnerability as Important with a CVSS 3.1 base score of 7.1. The attack vector is local, complexity is low, and no user interaction is required. While the CVSS vector indicates both high confidentiality and availability impacts, public documentation emphasizes information disclosure. An attacker who can execute code on the machine—even with minimal privileges—might exploit the flaw to gather sensitive data that could aid in further attacks or privilege escalation.
Only Windows 11 26H1 Is Affected
The CVE record targets Windows 11 version 26H1 on both x64 and Arm64 architectures. Windows 11 24H2, 25H2, and supported Windows Server releases are not listed as vulnerable. This is critical: 26H1 is not the standard annual feature update. Microsoft describes it as a release tailored for new hardware platforms introduced in 2026, meaning most existing PCs running 24H2 or 25H2 will never see this update. Organizations deploying brand-new hardware, however, must check their fleets for any 26H1 devices.
The Fix Was Actually Shipped in June
Here’s an unusual detail: the vulnerability was patched before it was publicly disclosed. Microsoft released build 28000.2269 on June 9, 2026, as part of the June cumulative update (KB5095051). That build already contains the fix for CVE-2026-50428, even though the CVE was only published in July. The July update, KB5101649 (build 28000.2525), supersedes the June package and includes the same correction plus additional security and reliability improvements. If you installed the June update, you’re already protected. If not, the July update is your direct path to resolution.
What It Means for You
For Home Users
If you’re on a standard Windows 11 PC running version 24H2 or 25H2, you are not affected. This flaw is specific to systems shipping with the 26H1 build, which are mostly new devices from 2026. Check your version by pressing Win+R, typing winver, and confirming the version number. If it says 24H2 or 25H2, you can ignore this CVE.
If you have a brand-new 26H1 device, Windows Update should automatically offer KB5101649. Install it and you’ll move to build 28000.2525, closing the vulnerability.
For IT Administrators
The biggest risk is for organizations that have deployed early 26H1 hardware—such as developer workstations, container hosts, or build servers—without realizing these machines may be outside normal update rings. The attack surface is narrow: exploitation requires an authenticated local attacker with low privileges. That makes shared workstations, lab environments, and systems accessible to contractors or third-party vendors more attractive targets.
The primary control is patch compliance. Immediately inventory any 26H1 devices in your estate. If you rely on Intune, Configuration Manager, or Windows Update for Business, query for systems reporting OS build below 28000.2269. Even if the July update hasn’t been approved yet for your deployment, verifying that the June update is installed achieves the same result. For those on an older build, deploy KB5101649 and confirm the build number afterward. There are no documented workarounds, so delaying the update leaves machines exposed.
For Developers and Container Enthusiasts
If you use Windows containers on 26H1, you are directly affected. The vulnerable driver is central to container isolation, and any process running within a container could potentially trigger the flaw (assuming the attacker has local access first). While no public exploit is available, the information disclosure could be chained with other exploits to escape container boundaries or steal secrets. Patch your development machines and container hosts immediately.
How We Got Here
Windows 11 26H1 entered the wild as a specialized release for the 2026 hardware wave. It’s not delivered via Windows Update to existing PCs; it comes preinstalled on new devices. Because of this bifurcation, administrators might not have realized that these systems require a separate patching workflow. The June 2026 patch cycle inadvertently already fixed the issue, but the public CVE disclosure on July 14 means the vulnerability is now widely known. Security teams must treat it with the same urgency as any other Important-rated flaw, even if the attack vector demands local access.
What to Do Now
- Check your version: On any devices you suspect might be new, verify Windows 11 version via Settings > System > About or
winver. The target is build 28000.2269 or later. - Apply the patch: Navigate to Windows Update and install KB5101649. This updates the OS to build 28000.2525 and includes all prior fixes.
- Verify the build: After updating, confirm the build number to ensure the patch took effect. If a device fails to update, investigate the update history and event logs.
- Enforce least privilege: Since exploitation requires low-level authenticated access, maintaining strict user permissions reduces the risk of an attacker gaining the necessary foothold.
- Monitor CVE developments: While the flaw is not currently exploited in the wild, keep an eye on threat intelligence feeds. If a proof-of-concept emerges, adjust your response urgency.
Outlook
Microsoft has not released technical details about the exact memory that can be read or how reliably the bug can be triggered. Security researchers may now probe the patched driver to understand the flaw, and a practical exploit could surface. For now, the priority is closing the window completely. Build compliance is your strongest defense. As the 26H1 hardware base grows, ensuring that all new machines are patched out of the box will become a critical part of your device provisioning process.