- What: Microsoft Windows Filtering Platform has a security feature bypass vulnerability.
- Impact: Attackers could bypass security features to gain unauthorized access.
We use optional cookies to improve your experience on our websites, such as through social media connections, and to display personalized advertising based on your online activity. If you reject optional cookies, only cookies necessary to provide you the services will be used. You may change your selection by clicking “Manage Cookies” at the bottom of the page. Privacy Statement Third-Party Cookies Accept Reject Manage cookies MSRC Customer Guidance Security Update Guide Vulnerabilities CVE-2026-32209 Windows Filtering Platform (WFP) Security Feature Bypass Vulnerability New On this page CVE-2026-32209 Subscribe RSS PowerShell API CSAF Security Vulnerability Released: May 12, 2026 Assigning CNA Microsoft CVE.org link CVE-2026-32209 Impact Security Feature Bypass Max Severity Important Weakness CWE-284: Improper Access Control CVSS Source Microsoft Vector String CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N/E:U/RL:O/RC:C Metrics CVSS:3.1 4.4 / 3.9 Base score metrics: 4.4 / Temporal score metrics: 3.9 Expand all Collapse all Metric Value Base score metrics(8) Attack Vector Local Attack Complexity Low Privileges Required Low User Interaction None Scope Unchanged Confidentiality Low Integrity Low Availability None Temporal score metrics(3) Exploit Code Maturity Unproven Remediation Level Official Fix Report Confidence Confirmed Please see Common Vulnerability Scoring System for more information on the definition of these metrics. Executive Summary Improper access control in Windows Filtering Platform (WFP) allows an authorized attacker to bypass a security feature locally. Exploitability The following table provides an exploitability assessment for this vulnerability at the time of original publication. Publicly disclosed No Exploited No Exploitability assessment Exploitation Unlikely FAQ What kind of security feature could be bypassed by successfully exploiting this vulnerability? Successfully exploiting this vulnerability could allow an attacker to bypass network security protections that rely on Fully Qualified Domain Name (FQDN)‑based rules, such as policies that block or allow network connections based on domain names. This could reduce the effectiveness of security features that depend on those domain‑based network controls. According to the CVSS metrics, successful exploitation of this vulnerability could lead to some loss of confidentiality (C:L), and integrity (I:L) but lead to no loss of availability (A:N). What is the impact of this vulnerability? Successful exploitation allows limited tampering with security configuration (low integrity impact) but does not expose sensitive data or disrupt system availability. In short, the vulnerability weakens specific security enforcement controls without causing data disclosure or service outages. Acknowledgements Adam Hassan with Microsoft Offensive Research & Security Engineering (MORSE) Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgements for more information. Security Updates To determine the support lifecycle for your software, see the Microsoft Support Lifecycle. Release date Descending Edit columns Download Filters Product Family Max Severity Impact Platform Clear Release date Product Platform Impact Max Severity Article Download Build Number Assigning CNA Customer Action Required Loading... Disclaimer The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. Revisions version revisionDate description 1.0 May 12, 2026 Information published. How satisfied are you with the MSRC Security Update Guide? Rating Broken Bad Below average Average Great! Your Privacy Choices Consumer Health Privacy