Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged local session
  2. Delivery
    Trigger Winlogon authentication or session-transition event
  3. Exploit
    Race freed memory object before reallocation
  4. Execution
    Groom heap with attacker-controlled data
  5. Persist
    Dereference dangling pointer in SYSTEM context
  6. Impact
    Execute arbitrary code as SYSTEM

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an existing low-privileged authenticated local session on the target Windows system (CVSS PR:L, AV:L) - remote unauthenticated attackers cannot trigger this flaw directly. High attack complexity (AC:H) indicates the attacker must win a race condition or achieve a specific heap layout; exploitation is not reliably deterministic and requires advanced memory manipulation skill. No user interaction from a second user is required (UI:N). Winlogon is active by default on all affected Windows systems, so no non-default configuration is required to expose the vulnerable code path. Exploitation is concretely limited by: the hard requirement for local authenticated code execution (rules out network-only attackers), high complexity heap conditions (rules out automated mass exploitation), and no scope change (S:U, meaning compromise is contained to the local system and does not directly pivot to adjacent systems).

Impact

The CVSS 3.1 vector AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H scores 7.0, with AC:H being the primary risk-reduction signal - exploitation is not straightforward and likely requires a race condition or precise heap-grooming technique that makes reliable weaponization non-trivial. PR:L confirms an existing authenticated local session is mandatory, eliminating remote unauthenticated attackers entirely. EPSS data was not provided in the input; exploitation probability cannot be independently quantified from available signals. No CISA KEV listing is present, and no POC is identified at time of analysis. The real-world priority is moderate-to-high specifically in multi-user Windows environments - Remote Desktop Session Hosts, VDI infrastructure, and shared Windows Server deployments - where untrusted low-privileged users already have local sessions and would benefit most from a privilege escalation primitive. In single-user workstation environments the practical risk is lower unless the attacker has already achieved initial access.

Exploit ScenarioDerived

An attacker with a low-privileged domain or local account on a Windows Remote Desktop Session Host triggers a race condition in Winlogon during a logon or session-transition event, causing a heap object to be freed while a stale pointer remains. By shaping the heap to place attacker-controlled data at the freed address before dereferencing occurs, the attacker corrupts Winlogon's execution flow and obtains SYSTEM-level code execution on the local machine. No public exploit identified at time of analysis; the AC:H rating implies reliable exploitation requires non-trivial heap-grooming expertise.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 11, 2026

Use-after-free in Windows Winlogon enables a locally authenticated attacker to escalate privileges to SYSTEM level across a broad range of Windows desktop and server editions spanning Windows 10 through Windows 11 26H1 and Windows Server 2012 through 2025. The CVSS 7.0 score (AV:L/AC:H/PR:L) reflects that exploitation requires an existing low-privileged foothold and high attack complexity, placing this squarely in the post-compromise privilege escalation category rather than an initial access vector. No public exploit identified at time of analysis; Microsoft has released patches covering all affected build branches.

RemediationAI

Apply Microsoft's released patches via Windows Update, WSUS, or Microsoft Update Catalog, targeting the minimum fixed builds identified in the affected products section - for example, Windows Server 2019 to build 10.0.17763.9115 or later, Windows 11 24H2 to 10.0.26100.9168 or later, and Windows Server 2025 to 10.0.26100.33296 or later. The full per-version build mapping is available at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-61939. Where immediate patching is not possible, restrict interactive and remote interactive logon rights to the minimum necessary accounts via Group Policy (User Rights Assignment: 'Allow log on locally' and 'Allow log on through Remote Desktop Services'), which reduces the pool of PR:L users who could attempt exploitation - note this may impact legitimate administrative workflows and requires careful scoping. Enabling Virtualization-Based Security and Credential Guard on supported editions further hardens the authentication subsystem but does not eliminate the underlying flaw.

Affected VersionsENISA

Windows Server 2019 10.0.17763.0 <10.0.17763.9115
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9168
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9115
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7663
Windows Server 2025 10.0.26100.0 <10.0.26100.33296
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7663
Windows Server 2012 6.2.9200.0 <6.2.9200.26279
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9418
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7517
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33296
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2704
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23337
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9168
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9115
Windows Server 2022 10.0.20348.0 <10.0.20348.5499
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26279
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23337
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9418
Windows Server 2016 10.0.14393.0 <10.0.14393.9418

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9418
euvd windows_10_version_1809 fix: 10.0.17763.9115
euvd windows_10_version_21h2 fix: 10.0.19044.7663
euvd windows_10_version_22h2 fix: 10.0.19045.7663
euvd windows_11_version_23h2 fix: 10.0.22631.7517
euvd windows_11_version_24h2 fix: 10.0.26100.9168
euvd windows_11_version_25h2 fix: 10.0.26200.9168
euvd windows_11_version_26h1 fix: 10.0.28000.2704
euvd windows_server_2012 fix: 6.2.9200.26279
euvd windows_server_2012_r2 fix: 6.3.9600.23337
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23337
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26279
euvd windows_server_2016 fix: 10.0.14393.9418
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9418
euvd windows_server_2019 fix: 10.0.17763.9115
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9115
euvd windows_server_2022 fix: 10.0.20348.5499
euvd windows_server_2025 fix: 10.0.26100.33296
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33296

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 19 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Winlogon (winlogon.exe) is the Windows process responsible for handling the secure attention sequence (Ctrl+Alt+Del), user authentication transitions, and the secure desktop - it runs persistently at SYSTEM integrity level. A use-after-free (CWE-416) arises when Winlogon frees a heap-allocated object but retains a dangling pointer that is subsequently dereferenced; an attacker who can time or trigger the reallocation of that freed memory region with attacker-controlled content can redirect execution within a SYSTEM-privileged process. Tags also include Denial of Service, indicating the UAF can destabilize the authentication stack without achieving code execution. Affected CPE scope per EUVD spans Windows 10 builds 14393-19045, Windows 11 builds 22631-28000, and Windows Server builds 9200-26100, covering both full and Server Core installation modes.

Know when Windows 10 1607 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local access and low-privileged authenticated session required; AC:H reflects race condition; SYSTEM-level code execution yields full C/I/A with no scope change.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Aug 11, 2026 - 18:19 EUVD
CVE Published
Aug 11, 2026 - 17:18 cve.org
HIGH 7.0

DescriptionCVE.org

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

Executive ViewAI

Why It Matters

Windows Winlogon vulnerability (CVE-2026-61939) enables locally authenticated attackers to escalate privileges to SYSTEM level across Windows 10-11 and Server 2012-2025. This post-compromise vulnerability converts initial user-level access into full administrative control, significantly expanding the blast radius from any user account compromise. Across your Windows estate, this enables attackers to bypass security controls and access critical business systems and data.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Ubiquitous
Winlogon is present in every Windows desktop and server deployment
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy