Skip to main content
Vulnerability Database/CVE-2026-97787

CVE-2026-97787: Windows Container Isolation Privilege Escalation

CVE-2026-97787 is a race condition flaw in Windows Container Isolation FS Filter Driver that enables local privilege escalation. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-97787 Overview

CVE-2026-97787 is a race condition vulnerability in the Windows Container Isolation FS Filter Driver (unionfs.sys). The flaw results from concurrent execution using a shared resource with improper synchronization [CWE-362]. An authorized local attacker can exploit the race window to elevate privileges on an affected Windows host. Microsoft published the advisory on 2026-10-13 and updated it the same day. No public exploit code or in-the-wild exploitation has been reported at the time of writing.

Critical Impact

Successful exploitation allows a low-privileged local user to elevate privileges, achieving high impact to confidentiality, integrity, and availability on the affected system.

Affected Products

Discovery Timeline

  • 2026-10-13 - CVE CVE-2026-97787 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-97787

Vulnerability Analysis

The defect lives in unionfs.sys, the file system filter driver that implements container isolation on Windows. The driver mediates file system operations between a container and the host, redirecting or layering I/O requests. Because the driver runs in kernel mode, any logic flaw in how it manages shared state creates a direct path to privilege escalation. CVE-2026-97787 is such a flaw: two concurrent threads can access a shared resource without proper synchronization, producing an exploitable race condition.

Root Cause

The underlying weakness is categorized as [CWE-362], concurrent execution using a shared resource with improper synchronization. In practice, this typically means the driver reads or validates a state value, then acts on it, without holding an exclusive lock across both operations. A second thread modifying the same state between the check and the use can cause the driver to operate on stale, attacker-controlled, or inconsistent data in kernel memory.

Attack Vector

Exploitation requires local access and low privileges on the target system. The attack complexity is high because the attacker must reliably win a timing race against the driver. No user interaction is required. A working exploit would issue tightly timed, parallel I/O requests against the container isolation filter driver to trigger the race window, then leverage the resulting kernel-mode inconsistency to execute code or modify objects at SYSTEM integrity.

No verified public proof-of-concept code is available. See the Microsoft Security Update Guide for CVE-2026-97787 for vendor technical details.

Detection Methods for CVE-2026-97787

Indicators of Compromise

  • No public indicators of compromise have been published for CVE-2026-97787.
  • Unexpected SYSTEM-level processes spawned from a low-privileged user session should be treated as suspicious.
  • Kernel crash dumps referencing unionfs.sys on systems running container workloads warrant investigation.

Detection Strategies

  • Monitor for abnormal process-token elevation where a child process runs as SYSTEM while the parent runs as a standard user.
  • Alert on repeated, high-frequency I/O operations against container isolation mount points from a single non-service process.
  • Correlate unionfs.sys driver faults with subsequent privileged process creation on the same host.

Monitoring Recommendations

  • Collect Windows kernel event telemetry and driver load events for unionfs.sys version changes.
  • Track Sysmon Event ID 1 (process creation) with integrity level transitions from Medium to System.
  • Baseline container runtime behavior so race-exploit attempts stand out as timing or I/O anomalies.

How to Mitigate CVE-2026-97787

Immediate Actions Required

  • Apply the Microsoft security update referenced in the MSRC advisory for CVE-2026-97787 across all affected Windows hosts.
  • Prioritize patching on multi-tenant hosts and workstations where untrusted users can run code locally.
  • Audit which systems load unionfs.sys and confirm each has received the update.

Patch Information

Microsoft has released a security update that addresses the improper synchronization in the Container Isolation FS Filter Driver. Consult the Microsoft Security Update Guide for CVE-2026-97787 for the specific KB articles and build numbers corresponding to each supported Windows version.

Workarounds

  • Where patching is delayed, restrict interactive and remote local logon rights to trusted administrative accounts only.
  • Disable or avoid using Windows container isolation features on hosts that do not require them, reducing exposure of unionfs.sys.
  • Enforce application control (for example, Windows Defender Application Control) to limit which binaries low-privileged users can execute.
bash
# Configuration example: verify unionfs.sys version after patching
Get-Item C:\Windows\System32\drivers\unionfs.sys | Select-Object VersionInfo

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.