CVE-2026-68820 is a use-after-free vulnerability in the Windows Ancillary Function Driver for WinSock, a kernel-mode component supporting the Windows Sockets API. An authorized attacker can exploit the flaw locally by executing a specially crafted application, escalating privileges to SYSTEM and gaining kernel access. Multiple Windows 10, Windows 11, and Windows Server releases are affected. Microsoft patched the vulnerability in its August 2026 security updates. Active exploitation has been linked to Lazarus Group's Operation Dream Job campaign.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 4 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
283 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Windows AFD use-after-free vulnerability mentioned as a contrast to CVE-2026-69836 because it reportedly has confirmed in-the-wild exploitation despite a lower CVSS score.
A Windows WinSock driver privilege-escalation flaw that is being exploited by Lazarus Group and is significant enough to have a CISA KEV remediation deadline for U.S. federal agencies.
A high-severity privilege escalation vulnerability affecting Windows Ancillary Function Driver for WinSock.
An Important-severity Windows elevation of privilege vulnerability affecting most versions of Windows. It is notable because the content states it is under active exploitation in the wild and would likely be used as part of a larger attack chain for local privilege escalation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.