Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability

IdentifiersCVE-2026-26177CWE-416· Use After Free

CVE-2026-26177 is an elevation-of-privilege vulnerability in the Windows Ancillary Function Driver for WinSock (AFD). Microsoft describes the flaw as a use-after-free condition. A locally authorized attacker with low privileges can exploit the bug to elevate privileges on the target system. Exploitation requires winning a race condition, which increases attack complexity, but no user interaction is required. Microsoft rated the issue Important and assigned CVSS 3.1 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to escalate from a low-privileged local context to SYSTEM privileges. With SYSTEM-level execution, the attacker can fully compromise the affected host, including accessing sensitive data, modifying system and security settings, installing or executing arbitrary code with elevated rights, and disrupting system availability.

Mitigation

If you can’t patch tonight, do this now.

No specific vendor workaround or mitigation is provided in the available advisory content. Until patching is completed, reduce exposure by limiting local access to trusted users, minimizing the number of low-privileged interactive accounts on affected systems, and monitoring for suspicious local privilege-escalation activity. Because exploitation is local, prioritizing patching on multi-user and high-value systems is advisable.

Remediation

Patch, then assume compromise.

Apply the official Microsoft security update for CVE-2026-26177 in the affected Windows component. Microsoft states that an official fix is available. Standard remediation should include deploying the relevant April 2026 Patch Tuesday update across affected Windows systems and validating successful installation through normal patch verification processes.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindowsoperating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.