Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local low-privileged access
-
DeliveryInvoke crafted call to Cryptographic Services
-
ExploitTrigger heap buffer overflow (CWE-122)
-
ExecutionCorrupt heap to hijack execution
-
PersistElevate to SYSTEM privileges
-
ImpactDisable defenses and move laterally
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 | Exploitation requires the attacker to already have local, authenticated access to the target host at low privilege (CVSS PR:L, AV:L) - this is a local privilege-escalation flaw, not a remotely reachable one, so an attacker must first obtain a foothold such as a standard user account or a compromised low-privilege process. No user interaction is required (UI:N) and attack complexity is low (AC:L), meaning once local access exists, triggering the heap overflow in Cryptographic Services is straightforward against affected default Windows installations with no special feature toggle or non-default configuration needed. The principal limiting factors are the mandatory local access and low-privilege authentication; hosts where untrusted users cannot log in locally (single-admin workstations without shared access) present a much smaller realistic attack surface than multi-user servers, terminal/RDS, and jump hosts. |
| Impact | Signals are internally consistent and point to a moderate, post-compromise risk. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) requires local access and at least low privileges, with high impact to confidentiality, integrity, and availability once triggered. EPSS is very low (0.04%, 13th percentile) and SSVC records Exploitation: none and Automatable: no, so mass or automated exploitation is not currently expected; however SSVC Technical Impact: total aligns with the C:H/I:H/A:H rating, confirming that successful exploitation yields full system control. There is no CISA KEV listing and no evidence of a public POC, so this is a real but non-urgent priority: it matters most as a chained escalation step after an attacker already has a foothold, not as a standalone remotely exploitable flaw. No key signals conflict - the CVSS local vector, low EPSS, and SSVC 'no automation' assessment all agree this is targeted-use escalation rather than a wormable threat. |
| Exploit ScenarioDerived | An attacker who has already gained a limited foothold on a Windows host - for example a standard domain user account, a compromised low-privilege service, or access to a shared terminal server - invokes a crafted operation against Windows Cryptographic Services that overflows a heap buffer, corrupting memory to elevate to SYSTEM. From there they disable security tooling, harvest credentials, and move laterally. No public exploit is identified at time of analysis, and the local attack vector with low complexity means a working exploit would be reliable but requires the attacker to already be on the machine. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 23, 2026
Local privilege escalation in Windows Cryptographic Services lets an authenticated low-privileged user corrupt heap memory (CWE-122) to gain SYSTEM-level control across supported Windows 10, Windows 11, and Windows Server builds. There is no public exploit identified at time of analysis and EPSS is very low (0.04%), but SSVC rates the technical impact as total, and Microsoft has released patches. Because it requires prior local access, it is a post-compromise escalation primitive rather than an initial-access threat.
RemediationAI
Apply the Microsoft security update for your specific Windows build as the primary remediation - Vendor-released patch is available; install the update that raises the OS to at least the fixed build for your SKU (for example Windows 10 22H2 to 10.0.19045.7291 or later, Windows 11 24H2 to 10.0.26100.8457 or later, Windows Server 2022 to 10.0.20348.5139 or later, Windows Server 2025 to 10.0.26100.32860 or later), as detailed in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40377. Because Cryptographic Services is a core OS service with no supported disable option, there is no clean feature-level workaround; interim compensating controls should focus on limiting who can obtain the local, low-privileged foothold required to trigger the flaw - enforce least privilege, restrict interactive and RDP logon rights to trusted accounts, apply application allowlisting to block untrusted local binaries, and monitor for anomalous privilege-escalation and crash activity in cryptsvc. These controls reduce the pool of potential attackers but do not remove the vulnerable code, so patching remains mandatory; prioritize multi-user, jump-host, and terminal/RDS servers where untrusted users share a host.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 21 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Windows Cryptographic Services (the cryptsvc / Cryptographic Services stack backing CryptoAPI, certificate handling, and related security functions) contains a heap-based buffer overflow classified as CWE-122. A heap overflow occurs when data written to a dynamically allocated buffer exceeds its bounds, corrupting adjacent heap metadata or object pointers; in a privileged service context this can be leveraged to overwrite control data and redirect execution or manipulate security tokens. The CPE data confirms the affected component ships as an integral part of the Windows operating system across client (Windows 10 1607/1809/21H2/22H2 and Windows 11 22H3/23H2/24H2/25H2/26H1) and server SKUs (Windows Server 2012 through 2025, including Server Core installations), meaning the vulnerable code path is a core OS service rather than an optional add-on.
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
Local privilege escalation needing a low-privileged foothold (AV:L, PR:L), no user interaction, low complexity, yielding full SYSTEM control (C:H/I:H/A:H) within the same host scope.
Primary rating from NVD.
CVSS VectorNVD
DescriptionCVE.org
Heap-based buffer overflow in Windows Cryptographic Services allows an authorized attacker to elevate privileges locally.
Executive ViewAI
CVE-2026-40377 is a privilege escalation in Windows Cryptographic Services affecting Windows 10, 11, and Server that allows authenticated local users to gain full SYSTEM-level control. This poses significant post-compromise escalation risk: once any user account on these systems is compromised through phishing or malware, an attacker gains immediate administrator control. With patches now available from Microsoft, timely deployment is critical to prevent attackers from escalating minor breaches into full system ownership.
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
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-29654
GHSA-m8m3-jvh9-rpcr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB