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-54913: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in Microsoft Windows 10 Version 1809

0
High
VulnerabilityCVE-2025-54913cvecve-2025-54913cwe-362cwe-416
Published: Tue Sep 09 2025 (09/09/2025, 17:00:59 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 10 Version 1809

Description

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows UI XAML Maps MapControlSettings allows an authorized attacker to elevate privileges locally.

AI-Powered Analysis

AILast updated: 10/02/2025, 00:54:32 UTC

Technical Analysis

CVE-2025-54913 is a high-severity local privilege escalation vulnerability affecting Microsoft Windows 10 Version 1809 (build 10.0.17763.0). The flaw arises from a race condition (CWE-362) in the Windows UI XAML Maps component, specifically within the MapControlSettings functionality. A race condition occurs when concurrent execution threads improperly synchronize access to shared resources, leading to unpredictable behavior. In this case, an authorized local attacker can exploit this improper synchronization to elevate privileges on the affected system. The vulnerability impacts confidentiality, integrity, and availability, as successful exploitation allows an attacker to gain higher privileges, potentially leading to full system compromise. The CVSS 3.1 base score is 7.8, reflecting a high severity with the following vector: Attack Vector: Local (AV:L), Attack Complexity: High (AC:H), Privileges Required: Low (PR:L), User Interaction: None (UI:N), Scope: Changed (S:C), and high impact on Confidentiality, Integrity, and Availability (C:H/I:H/A:H). No known exploits are currently reported in the wild, and no official patches have been linked yet. However, the vulnerability is publicly disclosed and should be addressed promptly. The race condition in a core UI component like Maps suggests that the flaw could be triggered by manipulating map-related settings or processes, potentially allowing attackers to bypass security boundaries and execute code with elevated privileges. The changed scope indicates that the vulnerability affects resources beyond the initially vulnerable component, increasing the risk of widespread system impact.

Potential Impact

For European organizations, this vulnerability poses a significant risk, especially for enterprises and government agencies still running Windows 10 Version 1809, which, despite being an older release, may remain in use in certain environments due to legacy applications or delayed upgrade cycles. Successful exploitation could allow attackers to escalate privileges locally, enabling them to install malware, exfiltrate sensitive data, or disrupt critical services. This is particularly concerning for sectors with high-value targets such as finance, healthcare, and critical infrastructure, where elevated privileges can facilitate lateral movement and persistent access. The lack of user interaction required for exploitation increases the threat level, as attackers with low privileges can automate attacks or leverage other footholds to trigger the vulnerability. Although no known exploits are currently active in the wild, the public disclosure and high CVSS score suggest that threat actors may develop exploits soon, increasing urgency for mitigation. Additionally, the changed scope and high impact on confidentiality, integrity, and availability mean that successful exploitation could have severe operational and reputational consequences for affected organizations.

Mitigation Recommendations

European organizations should prioritize upgrading systems running Windows 10 Version 1809 to a more recent, supported Windows version where this vulnerability is resolved. If immediate upgrade is not feasible, organizations should implement strict access controls to limit local user privileges, minimizing the number of users with low-level access that could exploit this flaw. Employ application whitelisting and endpoint detection and response (EDR) solutions to monitor for suspicious activity related to the Maps UI component or privilege escalation attempts. Network segmentation can help contain potential lateral movement following exploitation. Administrators should also audit and restrict the use of the Maps application or related services where possible. Since no official patch is currently linked, organizations should monitor Microsoft security advisories closely for updates or hotfixes. Additionally, applying security best practices such as enforcing least privilege, disabling unnecessary services, and maintaining up-to-date antivirus signatures will help reduce the attack surface. Finally, conducting internal penetration testing focused on local privilege escalation vectors can help identify and remediate environment-specific risks related to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
microsoft
Date Reserved
2025-07-31T18:54:19.613Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68c071e3ce6ed8307545ba85

Added to database: 9/9/2025, 6:28:51 PM

Last enriched: 10/2/2025, 12:54:32 AM

Last updated: 10/30/2025, 4:03:24 PM

Views: 44

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