Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid low-privilege credentials
-
DeliveryReach Event Log RPC over network
-
ExploitAbuse coarse access control
-
ExecutionInvoke privileged event-log operation
-
ImpactExecute arbitrary code on host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V8 - Authorization Insufficient granularity of access control
|
| Exploitation Conditions | Exploitation requires the attacker to already hold valid low-privilege authentication on the network (CVSS PR:L), and network reachability to the Windows Event Logging Service's remote interface (AV:N). No user interaction is required (UI:N) and attack complexity is low (AC:L). Limiting factors that reduce realistic risk: the attacker must possess working credentials rather than being fully unauthenticated, the SSVC assessment rates the attack as not automatable (so it is not suited to indiscriminate mass exploitation), and access to the remote event-log RPC endpoint must not be firewalled off from the attacker. The affected feature is the OS-level Event Logging Service present across the listed Windows client and Server builds, so no non-default configuration is needed beyond the service being reachable. |
| Impact | The signals point to a serious but not emergency-tier issue. The CVSS 3.1 base score is 8.8 (High) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - network reachable, low attack complexity, no user interaction, but requiring low-level authentication (PR:L). The SSVC framework reports Exploitation: none (no observed or public exploitation), Automatable: no (an attacker cannot reliably automate mass exploitation, consistent with the PR:L requirement for valid credentials), and Technical Impact: total, matching the C:H/I:H/A:H rating. EPSS is low at 0.61% (45th percentile), and the vulnerability is not in CISA KEV, so there is no evidence of active exploitation. The combination - high impact but requiring authentication and not automatable, with low EPSS and no KEV listing - suggests a genuine patch priority for domain and server environments (because a foothold account could pivot to code execution across the fleet) but not a drop-everything zero-day. No major conflicts exist in the data: the PR:L requirement is consistent with SSVC 'Automatable: no,' and the low EPSS aligns with SSVC 'Exploitation: none.' |
| Exploit ScenarioDerived | An attacker who has obtained a low-privileged but valid account on the network sends crafted requests to the Windows Event Logging Service over its remote RPC interface, abusing the service's overly coarse access controls to invoke privileged operations and execute arbitrary code on the target host. Because the CVSS vector is AV:N/AC:L/PR:L/UI:N, no victim interaction is needed and the technical steps are low-complexity, though the attacker must first hold credentials. No public proof-of-concept exploit has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Jul 22, 2026
Remote code execution in the Windows Event Logging Service affects a broad range of Microsoft Windows client and server releases (Windows 10 1607 through Windows 11 26H1, and Windows Server 2012 through 2025), where insufficient granularity of access controls (CWE-1220) lets an authenticated attacker with low privileges execute code over the network with high confidentiality, integrity, and availability impact. Microsoft has released patches for all affected builds. There is no public exploit identified at time of analysis and CISA has not listed it in KEV, with a low EPSS score of 0.61%.
Earlier versions of this analysis (1)
Remote code execution in the Microsoft Windows Event Logging Service allows an authenticated attacker with low privileges to execute code over a network after enticing a user into an interaction (UI:R), due to insufficient granularity of access control (CWE-1220). The flaw affects a broad range of Windows client and server builds from Windows 10 1607 and Windows Server 2012 through Windows 11 26H1 and Windows Server 2025. Microsoft has released a patch; there is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV.
RemediationAI
Apply the Microsoft security update for your specific OS build, referencing the vendor advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50502. Vendor-released patched builds are: Windows 10 1607/Server 2016 at 10.0.14393.9339, Windows 10 1809/Server 2019 at 10.0.17763.9020, Windows 10 21H2 at 10.0.19044.7548, Windows 10 22H2 at 10.0.19045.7548, Windows 11 24H2/Server 2025 at 10.0.26100.8875/10.0.26100.33158 respectively, Windows 11 25H2 at 10.0.26200.8875, Windows 11 26H1 at 10.0.28000.2269, Server 2012 at 6.2.9200.26226, Server 2012 R2 at 6.3.9600.23291, and Server 2022 at 10.0.20348.5386. As a compensating control until patched, restrict network access to the Event Log RPC/remote event-management interfaces by blocking or firewalling remote RPC and the RemoteEventLogSvc (135/tcp plus the dynamic RPC range) to only trusted management hosts, and tighten who holds valid low-privilege credentials since PR:L is required; note the trade-off that blocking remote event-log RPC will break legitimate remote log collection and centralized monitoring, so scope firewall rules to management subnets rather than applying them universally.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 32 packages in microsoft, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Windows Event Logging Service (the EventLog service, historically eventlog/wevtsvc), a core operating-system subsystem that collects, stores, and exposes system, security, and application event records and is reachable remotely via RPC. The root cause is classified as CWE-1220, Insufficient Granularity of Access Control, meaning the service enforces access decisions at too coarse a level, so an authenticated principal that should only have limited rights can reach privileged operations that permit code execution. The CPE data confirms the flaw spans the Microsoft Windows and Windows Server code base broadly - from Windows 10 Version 1607 and Server 2012 up through Windows 11 Version 26H1 and Server 2025, including Server Core installations - indicating the defective access-control logic lives in shared OS-level event-logging code rather than an edition-specific feature.
Know when Windows Server 2012 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
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable RPC service with no user interaction (AV:N/AC:L/UI:N) but requiring valid credentials (PR:L); code execution yields total compromise (C:H/I:H/A:H), scope unchanged.
Primary rating from Vendor (microsoft).
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
Insufficient granularity of access control in Windows Event Logging Service allows an authorized attacker to execute code over a network.
Executive ViewAI
Windows Event Logging Service contains a privilege escalation vulnerability affecting Windows 10, 11, and Server 2012-2025 instances, allowing any authenticated internal user to escalate to system-level code execution. This exposes your entire Windows infrastructure to lateral movement and data exfiltration risks. Vendor patches are available for all affected builds and must be deployed without delay.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Windows Server 2012
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary c
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit
EUVD-2026-44095
GHSA-qhxp-2823-2pw9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB