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-2025-62573: CWE-416: Use After Free in Microsoft Windows 10 Version 1809

0
High
VulnerabilityCVE-2025-62573cvecve-2025-62573cwe-416cwe-362
Published: Tue Dec 09 2025 (12/09/2025, 17:55:43 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 10 Version 1809

Description

Use after free in Windows DirectX allows an authorized attacker to elevate privileges locally.

AI-Powered Analysis

AILast updated: 12/09/2025, 18:23:42 UTC

Technical Analysis

CVE-2025-62573 is a use-after-free vulnerability identified in the DirectX component of Microsoft Windows 10 Version 1809 (build 10.0.17763.0). Use-after-free (CWE-416) vulnerabilities occur when a program continues to use a pointer after the memory it points to has been freed, leading to undefined behavior including memory corruption. In this case, an authorized attacker with local access and low privileges can exploit this flaw to elevate their privileges on the system. The vulnerability does not require user interaction but has a high attack complexity, meaning exploitation demands specific conditions or expertise. Successful exploitation can compromise confidentiality, integrity, and availability of the affected system, potentially allowing attackers to execute arbitrary code with elevated privileges. The CVSS v3.1 base score is 7.0 (high), reflecting the significant impact but limited attack vector (local only) and the requirement for existing privileges. No public exploits or patches are currently available, indicating the vulnerability is newly disclosed and may be targeted in the future. The affected product is Windows 10 Version 1809, a legacy operating system version that is still in use in some environments, particularly where upgrade cycles are slow or constrained by compatibility requirements. The vulnerability is categorized under CWE-416 (use after free) and also tagged with CWE-362, which relates to race conditions, suggesting a complex memory management flaw. This vulnerability is critical for organizations relying on legacy Windows 10 systems, especially those with multiple local users or where local access controls are weak.

Potential Impact

For European organizations, the impact of CVE-2025-62573 can be significant, particularly in sectors where legacy Windows 10 1809 systems remain operational, such as manufacturing, government, and critical infrastructure. An attacker with local access could leverage this vulnerability to escalate privileges, potentially gaining administrative control over affected machines. This could lead to unauthorized access to sensitive data, disruption of services, and deployment of further malware or ransomware. The confidentiality, integrity, and availability of systems are all at risk. Given the local attack vector, insider threats or attackers who have gained initial footholds through other means (e.g., phishing) could exploit this vulnerability to deepen their access. The lack of patches increases the window of exposure, and organizations with slow patch management or legacy system dependencies face heightened risk. The vulnerability could also be leveraged in targeted attacks against European enterprises with high-value assets, amplifying the potential damage.

Mitigation Recommendations

1. Immediately restrict local access to Windows 10 Version 1809 systems, enforcing strict access controls and monitoring for suspicious local activity. 2. Implement application whitelisting and endpoint detection and response (EDR) solutions to detect and block exploitation attempts. 3. Prioritize upgrading affected systems to supported Windows versions with active security updates to eliminate exposure to this vulnerability. 4. Until patches are available, consider isolating legacy systems from critical networks and sensitive data environments to limit potential impact. 5. Conduct thorough audits of user privileges and remove unnecessary local accounts or reduce privileges where possible. 6. Monitor system logs and security alerts for signs of privilege escalation or anomalous behavior indicative of exploitation attempts. 7. Prepare for rapid deployment of patches once Microsoft releases them, including testing in controlled environments to avoid operational disruptions. 8. Educate IT staff and users about the risks of local privilege escalation vulnerabilities and the importance of maintaining secure local access policies.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2025-10-15T17:11:21.222Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693867e974ebaa3babafb6fe

Added to database: 12/9/2025, 6:18:17 PM

Last enriched: 12/9/2025, 6:23:42 PM

Last updated: 12/11/2025, 7:33:37 AM

Views: 10

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats