SYSTEM privileges without any user interaction. While active attacks have not been observed, Microsoft classifies this issue as Exploitation More Likely, putting patch deployment firmly on the priority list for desktop and server administrators alike.
For defenders managing hybrid fleets across Windows 10, Windows 11, and Windows Server, local privilege escalation bugs in kernel-mode filter drivers are the quiet workhorses of post-compromise playbooks. Remote code execution flaws grab the headlines, sure, yet once an intruder lands a low-privilege foothold—through a phishing macro, a compromised service account, or an unpatched third-party utility—a reliable jump to SYSTEM is what turns a minor workstation incident into domain-wide trouble.
CVE-2026-88230 Advisory Snapshot and Official Facts
According to the official MSRC Update Guide dossier for CVE-2026-88230, the vulnerability carries the following authoritative metadata, severity ratings, and status assessments:
- CVE ID: CVE-2026-88230
- Title: Windows LUA File Virtualization Filter Driver Elevation of Privilege Vulnerability
- Severity: Important
- CVSS Base Score: 7.8
- CVSS Temporal Score: 6.8
- CVSS Vector:
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - Weakness (CWE): CWE-122
- Exploitation Assessment: Exploitation More Likely
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
MSRC's official description and advisory facts establish both the mechanics and the exact ceiling of an attack:
- Official Description: Heap-based buffer overflow in Windows LUAFV allows an authorized attacker to elevate privileges locally.
- Official Advisory Summary: Windows LUAFV Elevation of Privilege Vulnerability: Heap-based buffer overflow in Windows LUAFV allows an authorized attacker to elevate privileges locally.
- Privilege Impact Fact: What privileges could be gained by an attacker who successfully exploited this vulnerability? An attacker who successfully exploited this vulnerability could gain SYSTEM privileges.
Section Summary: CVE-2026-88230 is an Important-rated CWE-122 flaw in Windows LUAFV with a 7.8 base score, an Exploitation More Likely assessment, and direct SYSTEM privilege impact requiring customer patching.
Technical Context: Why Windows LUAFV and CWE-122 Matter
To understand why Microsoft flagged CVE-2026-88230 with an Exploitation More Likely rating despite Exploited: No and Publicly disclosed: No, it helps to look at the intersection of general Windows architecture knowledge and the specific CVSS metrics supplied in the advisory.
What Is the Windows LUA File Virtualization Filter Driver?
Synthesizing from general Windows internals knowledge, Least-Privileged User Account (LUA) File Virtualization—implemented via the luafv file system minifilter driver—exists to keep older, poorly behaved applications from crashing when run by standard users under User Account Control (UAC). Historically, plenty of legacy desktop software assumed every user held full administrative rights and tried to write configuration data or log files directly into protected system directories. Rather than letting those write operations fail outright, the LUA File Virtualization Filter Driver transparently redirects unauthorized file writes into a per-user virtual store directory inside the user's local profile.
Because file system minifilter drivers sit directly in the kernel I/O path and broker requests originating from standard user processes, any memory-corruption bug inside that translation layer bridges the boundary between low-privilege user space and privileged kernel execution.
Decoding the CVSS Vector and Heap-Based Buffer Overflow
Looking closely at the official vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C, the operational risk becomes crystal clear:
- Local Access, Low Barriers (
AV:L/AC:L/PR:L/UI:N): An attacker must already possess local execution capability with low privileges (PR:L), such as a standard domain user session or a compromised service account. However, attack complexity is low (AC:L) and zero user interaction is required (UI:N). Nobody has to click a UAC prompt or open a booby-trapped document once code is running locally. - Total Host Takeover (
S:U/C:H/I:H/A:H): High confidentiality, integrity, and availability ratings reflect what happens when an attacker gainsSYSTEMprivileges. At that tier, an adversary can disable endpoint security agents, harvest cached credentials, tamper with OS binaries, or pivot laterally. - Temporal Modifiers (
E:U/RL:O/RC:C): Unproven exploit maturity (E:U), an official fix (RL:O), and confirmed report confidence (RC:C) bring the temporal score from 7.8 down to 6.8—because Microsoft has already delivered official security updates across every affected platform.
From a general vulnerability-research standpoint, CWE-122 (heap-based buffer overflow) occurs when software writes data past the end of a dynamically allocated memory buffer. In kernel-mode components, security researchers routinely scrutinize patch diffs for CWE-122 flaws with low attack complexity (AC:L), which aligns with MSRC's proactive Exploitation More Likely designation. Could an organization afford to leave virtual desktop pools, jump hosts, or multi-session servers unpatched when any authenticated user could potentially trigger a kernel heap overflow? Hardly.
Section Summary: Because Windows LUAFV processes file operations initiated by standard users and requires low attack complexity without user interaction, CVE-2026-88230 presents an attractive target for post-exploitation privilege escalation.
Affected Windows and Windows Server Products, KBs, and Fixed Builds
The scope of CVE-2026-88230 spans 28 specific product configurations across Windows 10, Windows 11, and Windows Server (both standard Desktop Experience and Server Core installations). Notably, several modern Windows 11 branches (24H2, 25H2, and 26H2) as well as Windows Server 2025 list dual KB and fixed-build pairings in Microsoft's servicing matrix, whereas Windows 11 26H1 uses a distinct build and KB track (KB5132059 reaching 10.0.28000.3501).
The table below maps every affected product to its exact official KB article and vendor fixed build:
| Affected Product | Official KB(s) | Fixed Build(s) |
|---|---|---|
| Windows 10 Version 1607 for 32-bit Systems (x86) | KB5131291 | 10.0.14393.9688 |
| Windows 10 Version 1607 for x64-based Systems | KB5131291 | 10.0.14393.9688 |
| Windows 10 Version 1809 for 32-bit Systems (x86) | KB5131085 | 10.0.17763.9487 |
| Windows 10 Version 1809 for x64-based Systems | KB5131085 | 10.0.17763.9487 |
| Windows 10 Version 21H2 for 32-bit Systems (x86) | KB5131096 | 10.0.19044.7846 |
| Windows 10 Version 21H2 for ARM64-based Systems | KB5131096 | 10.0.19044.7846 |
| Windows 10 Version 21H2 for x64-based Systems | KB5131096 | 10.0.19044.7846 |
| Windows 10 Version 22H2 for 32-bit Systems (x86) | KB5131096 | 10.0.19045.7846 |
| Windows 10 Version 22H2 for ARM64-based Systems | KB5131096 | 10.0.19045.7846 |
| Windows 10 Version 22H2 for x64-based Systems | KB5131096 | 10.0.19045.7846 |
| Windows 11 Version 23H2 for ARM64-based Systems | KB5131087 | 10.0.22631.7711 |
| Windows 11 Version 23H2 for x64-based Systems | KB5131087 | 10.0.22631.7711 |
| Windows 11 Version 24H2 for ARM64-based Systems | KB5132043, KB5132061 | 10.0.26100.9911, 10.0.26100.9974 |
| Windows 11 Version 24H2 for x64-based Systems | KB5132043, KB5132061 | 10.0.26100.9911, 10.0.26100.9974 |
| Windows 11 Version 25H2 for ARM64-based Systems | KB5132043, KB5132061 | 10.0.26200.9911, 10.0.26200.9974 |
| Windows 11 Version 25H2 for x64-based Systems | KB5132043, KB5132061 | 10.0.26200.9911, 10.0.26200.9974 |
| Windows 11 Version 26H1 for ARM64-based Systems | KB5132059 | 10.0.28000.3501 |
| Windows 11 version 26H1 for x64-based Systems | KB5132059 | 10.0.28000.3501 |
| Windows 11 Version 26H2 for ARM64-based Systems | KB5132043, KB5132061 | 10.0.26300.9911, 10.0.26300.9974 |
| Windows 11 Version 26H2 for x64-based Systems | KB5132043, KB5132061 | 10.0.26300.9911, 10.0.26300.9974 |
| Windows Server 2016 (Server Core installation) (x64) | KB5131291 | 10.0.14393.9688 |
| Windows Server 2016 (x64) | KB5131291 | 10.0.14393.9688 |
| Windows Server 2019 (Server Core installation) (x64) | KB5131085 | 10.0.17763.9487 |
| Windows Server 2019 (x64) | KB5131085 | 10.0.17763.9487 |
| Windows Server 2022 (Server Core installation) (x64) | KB5131090 | 10.0.20348.5870 |
| Windows Server 2022 (x64) | KB5131090 | 10.0.20348.5870 |
| Windows Server 2025 (Server Core installation) (x64) | KB5131077, KB5131080 | 10.0.26100.33730, 10.0.26100.33822 |
| Windows Server 2025 (x64) | KB5131077, KB5131080 | 10.0.26100.33730, 10.0.26100.33822 |
Section Summary: Ten distinct Knowledge Base packages (KB5131077, KB5131080, KB5131085, KB5131087, KB5131090, KB5131096, KB5131291, KB5132043, KB5132059, and KB5132061) resolve CVE-2026-88230 across all supported architectures and editions in the advisory.
Exact Official Remediation Guidance by Platform
Because Customer action required: Yes applies to CVE-2026-88230, administrators must deploy the corresponding security update and verify the resulting OS build number. Below are the exact official remediation requirements for every affected product:
- For Windows 10 Version 1607 for 32-bit Systems (x86), install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows 10 Version 1607 for x64-based Systems, install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows 10 Version 1809 for 32-bit Systems (x86), install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows 10 Version 1809 for x64-based Systems, install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows 10 Version 21H2 for 32-bit Systems (x86), install KB5131096 to reach fixed build 10.0.19044.7846.
- For Windows 10 Version 21H2 for ARM64-based Systems, install KB5131096 to reach fixed build 10.0.19044.7846.
- For Windows 10 Version 21H2 for x64-based Systems, install KB5131096 to reach fixed build 10.0.19044.7846.
- For Windows 10 Version 22H2 for 32-bit Systems (x86), install KB5131096 to reach fixed build 10.0.19045.7846.
- For Windows 10 Version 22H2 for ARM64-based Systems, install KB5131096 to reach fixed build 10.0.19045.7846.
- For Windows 10 Version 22H2 for x64-based Systems, install KB5131096 to reach fixed build 10.0.19045.7846.
- For Windows 11 Version 23H2 for ARM64-based Systems, install KB5131087 to reach fixed build 10.0.22631.7711.
- For Windows 11 Version 23H2 for x64-based Systems, install KB5131087 to reach fixed build 10.0.22631.7711.
- For Windows 11 Version 24H2 for ARM64-based Systems, install KB5132043 to reach fixed build 10.0.26100.9911; install KB5132061 to reach fixed build 10.0.26100.9974.
- For Windows 11 Version 24H2 for x64-based Systems, install KB5132043 to reach fixed build 10.0.26100.9911; install KB5132061 to reach fixed build 10.0.26100.9974.
- For Windows 11 Version 25H2 for ARM64-based Systems, install KB5132043 to reach fixed build 10.0.26200.9911; install KB5132061 to reach fixed build 10.0.26200.9974.
- For Windows 11 Version 25H2 for x64-based Systems, install KB5132043 to reach fixed build 10.0.26200.9911; install KB5132061 to reach fixed build 10.0.26200.9974.
- For Windows 11 Version 26H1 for ARM64-based Systems, install KB5132059 to reach fixed build 10.0.28000.3501.
- For Windows 11 version 26H1 for x64-based Systems, install KB5132059 to reach fixed build 10.0.28000.3501.
- For Windows 11 Version 26H2 for ARM64-based Systems, install KB5132043 to reach fixed build 10.0.26300.9911; install KB5132061 to reach fixed build 10.0.26300.9974.
- For Windows 11 Version 26H2 for x64-based Systems, install KB5132043 to reach fixed build 10.0.26300.9911; install KB5132061 to reach fixed build 10.0.26300.9974.
- For Windows Server 2016 (Server Core installation) (x64), install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows Server 2016 (x64), install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows Server 2019 (Server Core installation) (x64), install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows Server 2019 (x64), install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows Server 2022 (Server Core installation) (x64), install KB5131090 to reach fixed build 10.0.20348.5870.
- For Windows Server 2022 (x64), install KB5131090 to reach fixed build 10.0.20348.5870.
- For Windows Server 2025 (Server Core installation) (x64), install KB5131077 to reach fixed build 10.0.26100.33730; install KB5131080 to reach fixed build 10.0.26100.33822.
- For Windows Server 2025 (x64), install KB5131077 to reach fixed build 10.0.26100.33730; install KB5131080 to reach fixed build 10.0.26100.33822.
Practical Deployment Priorities and Compliance Verification
Based on general enterprise patch management best practices, IT teams can streamline rollout and avoid false-negative compliance alerts by focusing on three practical checks:
- Prioritize Multi-User and Remote-Access Hosts First: Since CVE-2026-88230 requires an authorized local attacker (
PR:L), Remote Desktop Session Hosts, virtual desktop infrastructure (VDI) pools, developer build servers, and shared kiosk machines carry higher immediate exposure than isolated single-user appliances. - Account for Dual Fixed-Build Baselines in Compliance Queries: Notice that Windows 11 (
24H2,25H2,26H2) and Windows Server 2025 each provide two valid KB and fixed-build targets (KB5132043/.9911orKB5132061/.9974on those Windows 11 releases, andKB5131077/10.0.26100.33730orKB5131080/10.0.26100.33822on Windows Server 2025). Endpoint compliance scripts in Microsoft Intune or Configuration Manager should check that devices meet at least the minimum fixed build for their respective servicing channel rather than hardcoding only a single KB identifier. - Confirm Kernel-Driver Servicing via Reboot: Because
luafvoperates as a kernel-mode file system filter driver, staging the cumulative update alone is not enough—endpoints and Server Core instances must complete their required restart so the patched binary loads into memory and the OS build increments to the verified fixed build.
For ongoing discussions around cumulative update rollouts, Server Core servicing workflows, and Windows 11 patch verification scripts, check the Windows Updates and Security advisories sections right here on WindowsForum.com.
Section Summary: Prioritizing shared endpoints, building dual-KB awareness into compliance reporting, and completing host reboots ensures fleets close CVE-2026-88230 before proof-of-concept code can materialize.
References
- Official MSRC or vendor evidence msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com