Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as local user
-
DeliveryCall vulnerable csc.sys driver function
-
ExploitCraft oversized cache data structure
-
ExecutionTrigger heap buffer overflow
-
ImpactExecute arbitrary 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 | Authenticated local user account required. Windows Client Side Caching (csc.sys) driver must be present and accessible. Vulnerability requires direct interaction with csc.sys IOCTLs through legitimate local access. |
| Impact | Despite the high CVSS base score of 7.8, real-world risk is moderate and highly context-dependent. The attack vector requires local authenticated access (AV:L, PR:L), meaning an attacker must already have compromised a valid user account or have physical/RDP access to the target system. This significantly reduces the attack surface compared to remotely exploitable vulnerabilities. The low attack complexity (AC:L) and no user interaction requirement (UI:N) indicate that exploitation is straightforward once local access is achieved, making this a reliable privilege escalation primitive in multi-stage attacks. No confirmed active exploitation exists (not present in CISA KEV), and no public exploit code has been identified at time of analysis, reducing immediate urgency. However, the complete impact to confidentiality, integrity, and availability (C:H/I:H/A:H) means successful exploitation grants full SYSTEM control. From an SSVC perspective: exploitation status is none-detected, technical impact is total (full kernel compromise), and automatable is no (requires prior authentication). The broad affected product range-spanning all current Windows client and server versions-creates a wide exposure window in enterprise environments where patching cycles may lag. Organizations should prioritize this for systems with multiple users or those accessible to lower-privileged accounts, especially in environments where initial access vectors (phishing, exposed RDP) are prevalent. The availability of vendor patches mitigates risk substantially for organizations with mature patch management processes. |
| Exploit ScenarioDerived | An authenticated local user crafts a malicious request to the Windows csc.sys driver with oversized cache metadata. The heap overflow overwrites adjacent memory structures, allowing code execution with SYSTEM privileges for privilege escalation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 14, 2026
Local privilege escalation in Windows Client Side Caching driver (csc.sys) allows authenticated users with low privileges to gain SYSTEM-level access via heap-based buffer overflow exploitation. Affects all supported Windows 10, Windows 11, and Windows Server versions (2012 through 2025). Vendor-released patches are available from Microsoft as of early 2026. No public exploit identified at time of analysis, though the straightforward attack complexity (AC:L) and no user interaction requirement (
Earlier versions of this analysis (1)
Local privilege escalation in Windows Client Side Caching driver (csc.sys) allows authenticated users with low privileges to gain SYSTEM-level access via heap-based buffer overflow exploitation. Affects all supported Windows 10, Windows 11, and Windows Server versions (2012 through 2025). Vendor-released patches are available from Microsoft as of early 2026. No public exploit identified at time of analysis, though the straightforward attack complexity (AC:L) and no user interaction requirement (UI:N) make this a viable post-compromise escalation vector for attackers with initial local access.
RemediationAI
Apply security updates immediately from Microsoft's January 2026 Patch Tuesday release. Patched versions are Windows 10 1607/Server 2016 build 10.0.14393.9060 or later, Windows 10 1809/Server 2019 build 10.0.17763.8644 or later, Windows 10 21H2 build 10.0.19044.7184 or later, Windows 10 22H2 build 10.0.19045.7184 or later, Windows 11 22H3/23H2 build 10.0.22631.6936 or later, Windows 11 24H2/Server 2025 build 10.0.26100.32690 or later, Windows 11 25H2 build 10.0.26200.8246 or later, Windows 11 26H1 build 10.0.28000.1836 or later, Windows Server 2
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 36 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 Windows Client Side Caching driver (csc.sys) is a kernel-mode component responsible for offline file synchronization and caching network resources locally. This vulnerability stems from a heap-based buffer overflow (CWE-122), occurring when the driver improperly validates user-supplied input before copying data into a heap-allocated buffer. Because csc.sys operates in kernel space with SYSTEM privileges, successful exploitation allows an attacker to overflow the buffer with crafted data, overwriting adjacent memory structures to redirect execution flow or corrupt critical kernel objects. The local attack vector (AV:L) requires the attacker to already have authenticated access to the target system with low privileges (PR:L), positioning this as a second-stage attack following initial compromise. The vulnerability affects Windows kernel builds spanning over a decade of releases, from Windows Server 2012 (kernel 6.2) through the latest Windows 11 26H1 and Server 2025 (kernel 10.0.28000/26100), indicating a long-standing weakness in buffer handling logic within the CSC subsystem.
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Client Side Caching driver (csc.sys) allows an authorized attacker to elevate privileges locally.
Executive ViewAI
CVE-2026-26176 is a high-severity local privilege escalation in Windows Client Side Caching that allows any authenticated user to gain SYSTEM-level access, creating a critical post-compromise risk across all supported Windows 10, 11, and Server environments. This vulnerability directly impacts organizational security posture by enabling attackers with initial low-privilege access-whether from phishing, supply chain compromise, or lateral movement-to obtain full system control without additional user interaction, potentially affecting thousands of endpoints.
Apply vendor patch. If immediate patching is not feasible, restrict local administrative account usage, enforce application whitelisting to limit execution of exploitation tools, monitor for anomalous privilege escalation events via Windows Security event logs (Event ID 4672, 4673, 4674), and segment network access for critical services to reduce lateral movement risk from compromised low-privilege accounts.
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.
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-22414
GHSA-9cr5-9f63-xhxx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB