Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local foothold
-
DeliveryTarget Security Center channel endpoint
-
ExploitWin race to hijack communication channel
-
ExecutionExecute operations at elevated privilege
-
ImpactFull local system compromise
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V12 - Secure Communication Improper restriction of communication channel
|
| Exploitation Conditions | Exploitation requires the attacker to already have local, authenticated access to the host with at least low-level privileges (AV:L, PR:L) - this is not remotely reachable. The flaw is in the Windows Security Center component's communication channel (CWE-923, improper restriction of channel to intended endpoints); the high attack complexity (AC:H) indicates a non-trivial precondition, most consistent with winning a race/timing window or a specific transient state to redirect or spoof the channel, limiting reliable exploitation. No user interaction is needed (UI:N). Limiting factors for defenders: prior local access and valid credentials are mandatory, the AC:H barrier reduces reliability, and applying the fixed builds (e.g., 10.0.26100.9711 for 24H2, 10.0.19044.7807 for 10 22H2/21H2, 10.0.17763.9376 for 1809/Server 2019) fully remediates. |
| Impact | This is a locally-exploitable elevation-of-privilege flaw (CWE-923, improper restriction of a communication channel) in Windows Security Center, rated CVSS 7.0 (High) with vector AV:L/AC:H/PR:L/UI:N. The signals paint a moderate, not urgent, picture: the attacker must already have local access and valid low-level credentials (AV:L, PR:L), and the attack is of high complexity (AC:H), which typically implies a race condition or reliance on winning a timing/state window to hijack the communication channel - a meaningful barrier to reliable exploitation. Impact is severe once achieved (C:H/I:H/A:H, full compromise of the local system). There is no CISA KEV listing and no public exploit or POC referenced, so exploitation status is 'no public exploit identified at time of analysis.' No EPSS score was supplied, so widespread-exploitation probability cannot be quantified from the input. No SSVC decision data was provided. CONFLICT TO NOTE: the input Tags include 'Information Disclosure,' but the description and CVSS (I:H/A:H, not a read-only disclosure) describe privilege elevation - the tag appears mislabeled and should not drive triage. Net: a credible local-EoP patch-soon issue for Windows fleets, but the local-only vector plus AC:H and required authentication make it a lower real-world priority than a remote or low-complexity flaw of the same CVSS. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged authenticated foothold on a Windows host (e.g., via phishing or a standard user account) abuses the improperly restricted communication channel used by Windows Security Center to inject or redirect messages to a higher-privileged endpoint, winning a timing/state race (AC:H) to execute code or operations at elevated privilege. No user interaction is required (UI:N). No public exploit code was identified at the time of analysis, so exploitation would require the attacker to develop a working technique. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Local privilege escalation in Windows Security Center lets an attacker who already holds a foothold on a Windows host with low-level privileges (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.0 High) abuse an improperly restricted communication channel to obtain high confidentiality and integrity impact on the same machine. Only hosts that have not yet applied the current cumulative builds are affected, spanning Windows 10 1607 through 22H2, Windows 11 23H2 through 26H2, and Windows Server 2016/2019 including Server Core installations. The high attack complexity indicates a non-trivial precondition - most consistent with a race or transient-state condition that must be won to redirect or spoof the endpoint - so reliability is limited; prior local access and valid credentials are mandatory and no public exploit identified at time of analysis, with no CISA KEV listing.
RemediationAI
Vendor-released patches are available; apply the fixed cumulative builds from the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70212 - specifically 10.0.22631.7652 for Windows 11 23H2, 10.0.26100.9711 for 24H2, 10.0.26200.9711 for 25H2, 10.0.28000.3231 for 26H1, 10.0.26300.9711 for 26H2, 10.0.14393.9612 for Windows 10 1607 and Windows Server 2016 (including Server Core), 10.0.17763.9376 for Windows 10 1809 and Windows Server 2019 (including Server Core), and 10.0.19044.7807 for Windows 10 21H2/22H2. Windows 11 23H2 and the 26H1 build are on shorter servicing tracks, so confirm the build string after installation rather than relying on the monthly rollup name. Because exploitation requires the attacker to already be executing locally with valid low-privilege credentials, there is no meaningful network-level workaround; the practical compensating controls are reducing the number of accounts and sessions that can run code on the host (remove local admin from standard users, tighten RDP and remote-assistance exposure, and restrict interactive logon where the workload permits), which lowers the population of potential exploit origins but does not remove the flaw, and monitoring for unexpected local processes attempting to attach to or impersonate Windows Security Center IPC endpoints, which is detection rather than prevention and will produce benign noise from legitimate security tooling. Do not treat disabling Windows Security Center as a mitigation: it removes the vulnerable channel but also disables Defender/antivirus health reporting and weakens endpoint compliance posture, and on modern builds it is not user-disablable.
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 root cause is CWE-923, Improper Restriction of Communication Channel to Intended Endpoints. Windows Security Center (the WSC service / SecurityHealth component surface) exchanges data with other components over a local inter-process communication channel, and the flaw is that this channel does not adequately verify that the peer on the other end is a legitimate, intended endpoint. A local process able to place itself on that channel can impersonate or intercept the trusted endpoint, letting it influence privileged operations performed by the Security Center context and thereby elevate from a low-privileged local account to higher integrity. The unusual pairing of AV:L/PR:L with AC:H in the assessed vector - high complexity but only low privileges required - fits a race window or transient state that must be hit before the channel is redirected or spoofed, which is why the flaw is not remotely reachable and is not considered reliably exploitable. Because the vulnerable logic lives inside the operating system's security service rather than an optional application, exposure scales with the number of unpatched Windows endpoints and servers; Server Core SKUs carry the same vulnerable component with a smaller attack surface. Product identification is by OS build number (the input's EUVD record EUVD-2026-100339 enumerates the vulnerable build ranges); no CPE strings were supplied, so mapping should be done against the listed Windows 10, Windows 11, Windows Server 2016 and Windows Server 2019 build ranges.
Know when Windows 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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local EoP requiring an authenticated low-priv foothold (AV:L/PR:L) and a timing/state race typical of channel-restriction flaws (AC:H), yielding full local impact (C:H/I:H/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Improper restriction of communication channel to intended endpoints in Windows Security Center allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A high-severity local privilege escalation flaw in the Windows Security Center affects unpatched Windows 10, Windows 11, and Windows Server 2016/2019 systems, including Server Core deployments, allowing an attacker who already has a low-privileged foothold on a machine to elevate to full control of that host. The impact is contained to individual endpoints rather than the broader network, but successful elevation could expose sensitive data and allow tampering with system integrity on any affected device. Leadership should care because the affected population spans much of the organization's Windows estate, meaning remediation is largely a patch-management and endpoint-inventory exercise rather than an emergency incident response.
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
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
EUVD-2026-100339
GHSA-fjxp-c5gm-9h8w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB