Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
2DescriptionCVE.org
Access of resource using incompatible type ('type confusion') in Windows Ancillary Function Driver for WinSock allows an authorized attacker to elevate privileges locally.
AnalysisAI
Type confusion vulnerability in Windows Ancillary Function Driver for WinSock enables local authenticated users to escalate privileges to SYSTEM level on Windows 10 (versions 1607-22H2), Windows 11 (versions 22H3-26H1), and Windows Server 2012. Microsoft has released patches through their March 2026 security update cycle. The vulnerability requires low-privilege local access but no user interaction, making it a high-value target for post-compromise lateral movement and persistence. CVSS 7.8 reflects complete system compromise potential, though EPSS data and KEV status are not available for this future-dated CVE.
Technical ContextAI
The Windows Ancillary Function Driver for WinSock (AFD.sys) is a kernel-mode driver that provides core networking socket functionality for Windows applications. This vulnerability manifests as CWE-843 (Access of Resource Using Incompatible Type), commonly known as type confusion, where the driver incorrectly interprets memory objects as different types during socket operations. Type confusion in kernel drivers typically occurs when IOCTL handlers, callback functions, or object validation routines fail to verify object types before casting pointers, allowing attackers to trigger operations on mismatched data structures. The affected CPE strings indicate broad impact across Windows 10 builds from Anniversary Update (1607) through current versions, all Windows 11 releases including the latest 26H1 preview, and legacy Windows Server 2012 systems, suggesting the vulnerable code exists in a longstanding core networking component shared across these platforms.
RemediationAI
Apply the March 2026 cumulative security updates released by Microsoft for the affected Windows versions through Windows Update, WSUS, or Microsoft Update Catalog. Organizations should prioritize patching systems where low-privilege users have local access, including multi-user workstations, terminal servers, and systems accessible via remote desktop. For Windows Server 2012 environments nearing end-of-extended-support, consider accelerating migration to supported Windows Server versions as part of remediation strategy. If immediate patching is not feasible, implement compensating controls including: restricting local logon rights to essential users only via Group Policy (Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > 'Allow log on locally'), deploying application control policies (AppLocker/WDAC) to prevent execution of unauthorized binaries by low-privilege accounts, and enabling credential guard on Windows 10/11 Enterprise to protect against credential theft following privilege escalation. Monitor for unusual elevation of privileges using Windows Event IDs 4672 (special privileges assigned) and 4673 (privileged service called). Note that restricting local logon rights may impact legitimate user workflows and requires testing in non-production environments before deployment.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-29603
GHSA-j4xq-256r-c68q