Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local access
-
DeliveryInteract with Client License Service
-
ExploitTrigger heap buffer overflow (CWE-122)
-
ExecutionCorrupt heap and hijack control flow
-
ImpactExecute code as SYSTEM
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires pre-existing local, authenticated access as a low-privileged user (AV:L, PR:L) who can reach and interact with the Windows Client License Service; no user interaction is needed (UI:N). Exploitation is limited by high attack complexity (AC:H), characteristic of a heap-overflow condition that likely depends on a race window or specific heap state, reducing reliability and often requiring repeated attempts. There is no remote or unauthenticated path, which meaningfully constrains real-world risk to scenarios where an attacker has already achieved initial foothold on the host (notably multi-user, terminal-server, or shared workstations). |
| Impact | This is a local privilege-escalation flaw (CVSS 3.1 base 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) in the Windows Client License Service, with full confidentiality, integrity, and availability impact - consistent with attacker-controlled code execution at an elevated (likely SYSTEM) context. The real-world signals are moderate rather than urgent: the attack vector is local (AV:L), so an attacker must already have the ability to run code as a low-privileged user on the host (PR:L), and exploitation is rated high-complexity (AC:H), which for a heap overflow (CWE-122) typically implies a race condition or precise heap-grooming that reduces reliability. No EPSS score, no CISA KEV listing, and no public proof-of-concept were provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net: this is a credible second-stage escalation primitive useful after initial access, not a mass-exploitable remote threat - a 'patch in normal cycle, prioritize on multi-user/shared hosts' issue rather than an emergency. Note the CVSS vector and the description agree (both indicate local, authorized access), so there is no signal conflict to flag, but the absence of any EPSS/KEV/POC data means exploitation likelihood is unquantified rather than confirmed-low. |
| Exploit ScenarioDerived | An attacker who has already gained low-privileged code execution on a Windows host (e.g., via phishing or a compromised standard user account) interacts with the Client License Service to trigger a heap-based buffer overflow, corrupting heap memory to hijack execution and elevate to SYSTEM. Because the flaw is high-complexity (AC:H), the attacker likely needs to win a race or carefully groom the heap, so exploitation may require multiple attempts. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Local privilege escalation in the Windows Client License Service (ClipSVC) allows an authenticated low-privileged local attacker to execute arbitrary code at elevated integrity, potentially SYSTEM, via a heap-based buffer overflow (CWE-122). The vulnerability requires local access and high attack complexity (CVSS 3.1 vector AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base score 7.0), and there is no remote or unauthenticated path. No public exploit has been identified at the time of analysis, and exploitation is limited to scenarios where an attacker already has a foothold on the host, such as multi-user or terminal-server environments.
RemediationAI
Apply the Microsoft security update referenced in the MSRC advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-100201) once it is available; no exact patched version is specified in the provided data. If the update cannot be deployed immediately, consider disabling the Windows Client License Service (ClipSVC) if Microsoft Store and UWP app licensing are not required, noting that this will break Store app functionality. Additionally, restrict local interactive logon rights to trusted users only via Group Policy ('Allow log on locally') to limit the pool of potential attackers, and enforce least privilege by removing unnecessary administrative rights from standard users. These compensating controls reduce the attack surface but do not eliminate the underlying vulnerability.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 13 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Windows Client License Service (ClipSVC) is a Windows service that manages licensing for Microsoft Store applications, typically running with SYSTEM privileges. The vulnerability is a heap-based buffer overflow (CWE-122), where improper bounds checking on heap-allocated memory allows an attacker to write beyond the allocated buffer, corrupting adjacent heap metadata and potentially leading to arbitrary code execution. Exploitation requires a low-privileged local attacker to trigger the overflow, but the high attack complexity (AC:H) suggests that success depends on precise heap grooming, a race condition, or a specific heap state, making reliable exploitation difficult and often requiring multiple attempts. There are no remote attack vectors, and no user interaction is needed (UI:N).
Know when the next one hits your stack
- 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:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local EoP by an authorized low-privileged user (AV:L/PR:L); heap overflow implies a race/grooming requirement (AC:H); successful control-flow hijack yields full C/I/A impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Client License Service allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A local privilege-escalation flaw in the Windows Client License Service (ClipSVC) could allow an authenticated user with existing access to a Windows host to elevate to SYSTEM-level privileges, potentially leading to full control of that endpoint. This risk is most acute for shared or multi-user Windows environments, such as terminal servers and remote desktop hosts, where many users already have local access. Because no vendor patch is currently available, leadership should treat this as a manageable but urgent exposure requiring hardening and monitoring rather than mass remediation.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting local interactive logon and RDP to trusted users, enforcing least privilege and removing unnecessary local administrator rights, enabling application control/allowlisting, monitoring ClipSVC and license-related process activity, and considering service disablement only where business impact is acceptable.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
EUVD-2026-100314
GHSA-h5x4-5647-ph8q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB