Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local foothold
-
DeliveryOpen WinSock/AFD socket objects
-
ExploitTrigger use-after-free race in afd.sys
-
ExecutionReclaim freed kernel allocation with controlled data
-
PersistCorrupt kernel memory for code execution
-
ImpactElevate to SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already possess local, authenticated code-execution ability on the target (PR:L, AV:L) - there is no remote or network-facing vector and no path from an unauthenticated position. The attacker must exercise the Ancillary Function Driver for WinSock (afd.sys) socket code paths to trigger the use-after-free. The principal limiting factor is high attack complexity (AC:H): the UAF is a timing/race-dependent condition the attacker must reliably win, which resists automation (SSVC Automatable: no). No user interaction is required (UI:N), and default configurations are affected since AFD is loaded on all Windows installs, but the mandatory pre-existing local foothold meaningfully narrows realistic exploitation to shared, multi-user, or already-compromised hosts. |
| Impact | Signals are consistent and point to a moderate, not emergency, priority. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U) describes a local-only use-after-free requiring the attacker to already have low-privilege authenticated code execution on the host and to win a high-complexity condition (typical of UAF race windows), yielding total confidentiality/integrity/availability impact (C:H/I:H/A:H) - hence the 7.0 base score. CISA's SSVC framework corroborates this restraint: Exploitation=none (no observed exploitation), Automatable=no (cannot be reliably scripted at scale, matching AC:H), and Technical Impact=total (matching full kernel compromise on success). There is no CISA KEV listing and no public exploit identified at time of analysis, and no EPSS probability was supplied. Net: this is a genuine privilege-escalation primitive in a kernel driver - valuable as a second-stage chain link for an attacker who already has a foothold - but it is not a wormable, remote, or low-effort issue. Prioritize via normal Patch Tuesday cadence, with elevated attention on multi-user and shared/terminal-server hosts where untrusted users hold local accounts. No conflicting signals were found in the provided data; the main missing input is an EPSS score. |
| Exploit ScenarioDerived | An attacker who has already obtained low-privileged authenticated access to a Windows host (e.g., via phishing, a compromised service account, or a standard user login on a shared machine) runs a local program that rapidly opens, uses, and frees WinSock/AFD objects to trigger the use-after-free race in afd.sys. On winning the race, they reclaim the freed kernel allocation with controlled data and corrupt kernel memory to execute code at SYSTEM. No public exploit code is identified at time of analysis, and the high attack complexity (AC:H) means success depends on reliably winning a timing-sensitive race. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in Microsoft's Windows Ancillary Function Driver for WinSock (afd.sys) lets an authenticated attacker who already has code execution on a target machine trigger a use-after-free in the kernel socket-handling paths and elevate to SYSTEM. The flaw is rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) - it is strictly local and requires a pre-existing foothold, and the race/timing nature of the bug makes it hard to trigger reliably, which is why CISA's SSVC rates exploitation as 'none' and automatable as 'no'. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so the risk is assessed as moderate rather than emergency priority; Microsoft has released fixes, with EUVD tracking the affected builds under EUVD-2026-99879.
RemediationAI
Apply the vendor-released patch from Microsoft - per the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70237), fixed builds for the EUVD-tracked branches include 10.0.14393.9612 (Windows 10 1607 / Server 2016), 10.0.17763.9376 (Windows 10 1809 / Server 2019), 10.0.19044.7807 (Windows 10 21H2/22H2), 10.0.22631.7652 (Windows 11 23H2), 10.0.26100.9711 (Windows 11 24H2), 10.0.26100.33650 (Windows Server 2025), 10.0.26200.9711 (Windows 11 25H2), 10.0.26300.9711 (Windows 11 26H2), 10.0.28000.3231 (Windows 11 26H1), 10.0.20348.5761 (Windows Server 2022), 6.2.9200.26434 (Server 2012) and 6.3.9600.23470 (Server 2012 R2); verify the exact KB against the advisory before deployment. Because afd.sys is a core, always-loaded networking component, there is no supported way to disable, unload or block the driver itself - doing so would break all Winsock/network functionality on the host, so that is not a viable workaround. Realistic compensating controls therefore focus on removing the required local foothold and limiting exposure: restrict interactive and RDP logon rights so only trusted, audited accounts can run code on the host, and reduce the number of users on densely shared or multi-session systems (the primary exploitation scenario), accepting the obvious operational trade-off of reduced multi-user access; enable protections that blunt post-exploitation token theft such as Credential Guard and LSASS protection (which raise the cost of converting kernel elevation into domain credentials but do not prevent the UAF itself); keep EDR/kernel telemetry enabled and alert on suspicious afd.sys-related pool corruption, unexpected socket churn from non-network processes, or crashes tagged as memory corruption; and treat any host that has already been compromised by a local attacker as requiring full rebuild after patching, since an attacker with SYSTEM could have established persistence. Microsoft's assessment attributes the report to secure@microsoft.com, and patch availability is confirmed but not independently verified for every build listed above.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 20 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Ancillary Function Driver for WinSock (afd.sys) is the kernel-mode driver that underpins the Windows Sockets (Winsock) API, servicing socket creation, connection and teardown requests on behalf of user-mode Winsock calls. The vulnerability is a CWE-416 use-after-free: a socket-related kernel object (such as an AFD endpoint or connection structure) can be freed while a reference to it is still in use, resulting in memory corruption in kernel pool memory. Because the trigger is a race/timing condition in AFD's socket code paths, exploitation requires the attacker to win that window reliably (AC:H), and the SSVC assessment rates the issue as 'not automatable' while assigning a total technical impact if exploited - the classic outcome of a kernel UAF being pool grooming and replacement of the freed object to achieve controlled kernel reads/writes and token privilege escalation. The attack surface is limited to local, authenticated interaction (AV:L, PR:L, UI:N) via local socket operations; there is no remote or network-facing vector, but AFD is loaded by default on all affected Windows installations, so every unpatched host is technically susceptible once an attacker has local code execution. Relevant tags describe denial of service and general memory corruption, consistent with a UAF in a kernel driver, and no CPE strings were supplied to further constrain the component mapping.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only UAF needing a pre-existing low-priv account (AV:L/PR:L), success gated on winning a race (AC:H), yielding full SYSTEM compromise (C:H/I:H/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Ancillary Function Driver for WinSock allows an authorized attacker to elevate privileges locally.
Executive ViewAI
Microsoft Windows Ancillary Function Driver for WinSock (afd.sys) contains a local privilege-escalation issue that could allow an authenticated attacker with an existing foothold to gain SYSTEM-level control on affected Windows endpoints and servers. Because exploitation requires local access and a pre-existing code-execution capability, no public exploit identified at time of analysis, and vendor fixes are available, the immediate organizational risk is moderate rather than emergency-level. Leadership should care because successful escalation on a compromised host can let an intruder deepen access, disable controls, and pivot to higher-value systems, making timely patching and endpoint hardening important for multi-user and high-value Windows assets.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-99879
GHSA-8g6j-rj6q-hr2h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB