Patch tracker / CVE reference / CVE-2025-59242
CVE-2025-59242
CVE-2025-59242 is a high severity Microsoft vulnerability with a CVSS score of 7.8. Microsoft has shipped the fix: deploy one of the 14 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Risk summary
Not in the CISA KEV catalog. EPSS exploit probability 6.0%. CVSS 7.8 (High).
This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.
The Ancillary Function Driver for WinSock (afd.sys), a kernel driver invoked by essentially all socket activity, carries this Critical (CVSS 9.9) elevation of privilege flaw on Windows 10 1809 and Windows Server 2019. AFD has been exploited in the wild in previous years, which lends weight to a new Critical finding despite the 6 percent EPSS score and no current KEV entry.
Do this: Push the fix to Server 2019 systems first; a socket-layer kernel escalation is most dangerous on multi-user servers.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2025-59242
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2025-59242
Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5066586, KB5066780, KB5066782, KB5066791, KB5066793, KB5066835, KB5066836, KB5066837, KB5066872, KB5066873, KB5066874, KB5066875, KB5066876, KB5066877 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.
Apply the Microsoft security updates below to fix CVE-2025-59242. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.
Scope and sources
- Affected products
- Fixed by the same updates
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.