Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-20810: CWE-590: Free of Memory not on the Heap in Microsoft Windows 10 Version 1809

0
High
VulnerabilityCVE-2026-20810cvecve-2026-20810cwe-590
Published: Tue Jan 13 2026 (01/13/2026, 17:56:10 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 10 Version 1809

Description

Free of memory not on the heap in Windows Ancillary Function Driver for WinSock allows an authorized attacker to elevate privileges locally.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/02/2026, 00:35:34 UTC

Technical Analysis

CVE-2026-20810 is a vulnerability classified under CWE-590, which involves the improper freeing of memory not allocated on the heap, leading to undefined behavior and potential security breaches. This flaw exists in the Windows Ancillary Function Driver for WinSock on Microsoft Windows 10 Version 1809 (build 17763.0). The vulnerability allows an authorized local attacker to exploit the improper memory management to elevate their privileges on the affected system. Specifically, the attacker can trigger a condition where memory that was not allocated on the heap is freed, causing corruption or unexpected behavior in kernel-mode components. This can lead to execution of arbitrary code with elevated privileges, compromising system confidentiality, integrity, and availability. The CVSS v3.1 base score is 7.8, reflecting a high severity due to local attack vector, low attack complexity, required privileges, and no user interaction needed. Although no public exploits are currently known, the vulnerability poses a significant risk to systems that remain unpatched. The flaw is particularly critical because it affects a core networking driver, potentially impacting many Windows 10 systems still running this legacy version. The absence of a patch link suggests that mitigation currently relies on workarounds and limiting local access until an official update is released.

Potential Impact

If exploited, this vulnerability allows attackers with local access to escalate their privileges to SYSTEM or equivalent, enabling full control over the affected machine. This can lead to unauthorized access to sensitive data, installation of persistent malware, disabling of security controls, and disruption of system availability. Organizations relying on Windows 10 Version 1809, especially those with legacy systems or limited patch management capabilities, face increased risk of internal threats or lateral movement by attackers who have gained initial footholds. The compromise of such systems can cascade into broader network breaches, data exfiltration, and operational disruption. Given the high CVSS score and the critical nature of the affected component (WinSock driver), the impact extends to both enterprise and government environments where Windows 10 1809 remains in use. The lack of known exploits in the wild currently reduces immediate risk but does not diminish the urgency for mitigation due to the potential for rapid weaponization.

Mitigation Recommendations

1. Apply official security patches from Microsoft as soon as they become available for Windows 10 Version 1809. 2. Until patches are released, restrict local user access to trusted personnel only and enforce strict access controls on systems running this OS version. 3. Employ application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious activities related to the WinSock driver and memory management anomalies. 4. Disable or limit unnecessary local accounts and services that could be leveraged to exploit this vulnerability. 5. Conduct regular system audits and vulnerability scans to identify unpatched Windows 10 1809 systems. 6. Consider upgrading affected systems to a supported and patched version of Windows where feasible to reduce exposure. 7. Monitor security advisories from Microsoft and threat intelligence sources for updates or emerging exploit reports. 8. Implement network segmentation to limit the impact of a compromised host. These steps go beyond generic advice by focusing on controlling local access, monitoring specific driver behavior, and prioritizing patch management for legacy Windows versions.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2025-12-03T05:54:20.372Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69668adaa60475309f9adf4a

Added to database: 1/13/2026, 6:11:38 PM

Last enriched: 3/2/2026, 12:35:34 AM

Last updated: 3/26/2026, 10:20:31 AM

Views: 50

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses