Abstract illustration of connected devices separated by a protected security boundary.
Microsoft has issued fixes for CVE-2026-108414, an Important-rated Windows vulnerability that could let an authorized local attacker gain SYSTEM privileges. The crucial qualification is configuration: exploitation requires the optional Projected File System feature to be enabled and its filter to be attached to a volume. Microsoft says systems without that configuration are not affected.

For administrators, that makes this a two-part task: establish which machines meet the exposure conditions, then match each affected operating system to its exact update and fixed build. An operating-system entry in the advisory is a starting point—not, by itself, proof that a particular machine is exposed.

Abstract illustration of connected devices separated by a protected security boundary. Vulnerability details and Microsoft’s assessment​

Microsoft’s Security Response Center identifies the issue as Windows Projected File System Filter Driver Elevation of Privilege Vulnerability.

The description states that a use-after-free flaw in Windows Projected File System Filter Driver allows an authorized attacker to elevate privileges locally. Microsoft classifies the weakness as CWE-416 and confirms that successful exploitation could grant SYSTEM privileges.

FieldMicrosoft advisory value
CVECVE-2026-108414
SeverityImportant
CVSS base score7.0
CVSS temporal score6.1
CWECWE-416
Exploitation assessmentExploitation Less Likely

CVSS vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Microsoft’s advisory records these statuses:

  • Publicly disclosed: No
  • Exploited: No
  • Customer action required: Yes

The vector describes a local attack requiring low privileges, with high attack complexity and no user interaction. It assigns high potential impacts to confidentiality, integrity, and availability, with unchanged scope.

Microsoft specifically explains the AC:H rating through the configuration prerequisites: the optional Projected File System feature must be enabled, and its filter must be attached to a volume. Both conditions matter.

Practical takeaway: “Exploitation Less Likely” is an assessment of exploitation prospects, not a reduction in the stated outcome. On a qualifying system, successful exploitation could still yield SYSTEM privileges.

How to prioritize affected machines​

The advisory supports a more precise response than treating every listed Windows installation as equally exposed.

  1. Identify the exact operating system and architecture. Use the product-specific remediation entries below rather than choosing an update from a similar-looking build number.
  2. Establish whether the exposure configuration exists. Confirm both that the optional Projected File System feature is enabled and that its filter is attached to a volume.
  3. Prioritize systems meeting both conditions. This prioritization follows directly from Microsoft’s stated exploitation requirements.
  4. Deploy the applicable fix and verify the resulting build. Match the installed result to the correct product-specific mapping, not merely to a KB number used elsewhere.

This is an administrative interpretation of Microsoft’s advisory, not an additional vendor workaround. The distinction is useful: exposure assessment answers whether the stated attack conditions exist; update verification answers whether the applicable fix has been deployed.

Windows 10 remediation and fixed builds​

Microsoft lists the following exact product-specific remediation values:

  • 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.

The important verification detail is that KB5131096 maps to different fixed builds for the two release branches. A compliance check should preserve that distinction rather than treating the KB as a single universal build target.

Windows 11 remediation and fixed builds​

The Windows 11 entries cover both ARM64-based and x64-based systems, with release-specific mappings:

  • 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.

Here, KB5132043 and KB5132061 each map to three distinct release-specific builds. The practical lesson is straightforward: a shared update identifier does not make the resulting build interchangeable across Windows releases.

Windows Server remediation and fixed builds​

Microsoft includes both Server Core installation and other listed server entries:

  • 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.

Server Core installations are explicitly included in the affected-product mappings. Their exposure still depends on the same feature-and-filter configuration Microsoft describes; installation type alone is not the deciding factor.

The compliance trap: similar builds, different fixes​

A particularly useful comparison in Microsoft’s mappings concerns Windows 11 Version 24H2 for x64-based Systems and Windows Server 2025 (x64). Their listed fixed builds share the 10.0.26100 prefix, but their applicable KBs and complete fixed-build values differ.

That makes a prefix-only compliance rule inadequate for this advisory. Administrators should retain three pieces of information together:

  • The exact affected product.
  • The applicable KB.
  • The complete corresponding fixed build.

Likewise, an exposure inventory should retain both configuration prerequisites rather than a single “feature enabled” flag. These are separate checks, and collapsing either pair loses information that Microsoft’s advisory makes material.

Bottom line​

CVE-2026-108414 is a local privilege-escalation vulnerability with a serious potential outcome but a specific exposure boundary. Microsoft rates it Important, assesses exploitation as less likely, and provides product-specific fixes.

The sound response is neither blanket alarm nor dismissal: identify systems with the required Projected File System configuration, deploy the matching update, and verify the full build against the exact product entry. For this vulnerability, configuration precision and patch precision belong in the same checklist.

 

References

  1. Official MSRC or vendor evidence api.msrc.microsoft.com
  2. Official MSRC or vendor evidence msrc.microsoft.com
  3. Official MSRC or vendor evidence api.msrc.microsoft.com