CVE Alert: CVE-2025-59505 – Microsoft – Windows 10 Version 1809

CVE-2025-59505

HIGHNo exploitation known

Double free in Windows Smart Card allows an authorized attacker to elevate privileges locally.

CVSS v3.1 (7.8)
Vendor
Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft, Microsoft
Product
Windows 10 Version 1809, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022, Windows 10 Version 21H2, Windows 10 Version 22H2, Windows Server 2025 (Server Core installation), Windows 11 Version 25H2, Windows 11 version 22H3, Windows 11 Version 23H2, Windows Server 2022, 23H2 Edition (Server Core installation), Windows 11 Version 24H2, Windows Server 2025, Windows 10 Version 1607, Windows Server 2016, Windows Server 2016 (Server Core installation), Windows Server 2012, Windows Server 2012 (Server Core installation), Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation)
Versions
10.0.17763.0 lt 10.0.17763.8027 | 10.0.17763.0 lt 10.0.17763.8027 | 10.0.17763.0 lt 10.0.17763.8027 | 10.0.20348.0 lt 10.0.20348.4405 | 10.0.19044.0 lt 10.0.19044.6575 | 10.0.19045.0 lt 10.0.19045.6575 | 10.0.26100.0 lt 10.0.26100.7171 | 10.0.26200.0 lt 10.0.26200.7171 | 10.0.22631.0 lt 10.0.22631.6199 | 10.0.22631.0 lt 10.0.22631.6199 | 10.0.25398.0 lt 10.0.25398.1965 | 10.0.26100.0 lt 10.0.26100.7171 | 10.0.26100.0 lt 10.0.26100.7171 | 10.0.14393.0 lt 10.0.14393.8594 | 10.0.14393.0 lt 10.0.14393.8594 | 10.0.14393.0 lt 10.0.14393.8594 | 6.2.9200.0 lt 6.2.9200.25768 | 6.2.9200.0 lt 6.2.9200.25768 | 6.3.9600.0 lt 6.3.9600.22869 | 6.3.9600.0 lt 6.3.9600.22869
CWE
CWE-415, CWE-415: Double Free
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Published
2025-11-11T17:59:13.264Z
Updated
2025-11-11T17:59:13.264Z

AI Summary Analysis

Risk verdict

High risk of local privilege escalation; an official fix is available, so patch promptly to reduce exposure.

Why this matters

The double-free flaw in the Windows Smart Card Reader enables an authorized local user to elevate privileges with high impact on confidentiality, integrity, and availability. In environments relying on Smart Card authentication, an attacker who gains local access could move from a foothold to higher privileges, potentially compromising security controls and administrative functions.

Most likely attack path

Exploitation requires local access (no user interaction). An attacker with low-privilege local capability could trigger the vulnerability via the Smart Card subsystem, escalating to higher rights within the same scope. This enables lateral movement within the compromised host and preservation of access, subject to the unchanged scope constraint.

Who is most exposed

Enterprise endpoints and servers that rely on Windows Smart Card authentication are at risk, particularly organisations using affected Windows versions listed in the advisory. Any environment with Smart Card logon, admin consoles, or remote management tied to these platforms is a candidate for exploitation.

Detection ideas

  • Look for unexpected SYSTEM-level process launches originating from Smart Card-related services.
  • Detect memory-corruption crashes or fault logs linked to Smart Card components.
  • Monitor for anomalous local logon attempts tied to smart card events or extended privilege changes.
  • Alert on Smart Card service crashes or restarts outside maintenance windows.
  • Correlate authentication events with sudden privilege elevation indicators.

Mitigation and prioritisation

  • Apply the Microsoft fix via Windows Update/SSP as a high-priority patch rollout; test in staging before broad deployment.
  • If patching is delayed, enforce compensating controls: restrict local logon on high-value systems, segment admin workstations, and limit Smart Card access where feasible.
  • Enhance detection: tighten Smart Card event monitoring, enable strict ASLR/DEP, and deploy enhanced fault logging.
  • Change-management: notify stakeholders, verify asset coverage, and map affected endpoints to patch status; document rollback if issues arise.

Support Our Work

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

AI APIs OSINT driven New features