Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege local or RDP session
-
DeliveryCraft command-injection payload targeting PCA service input
-
ExploitSubmit payload to PCA service processing path
-
ExecutionPCA executes injected commands as SYSTEM
-
ImpactAchieve full local system compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Command injection prevention
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 an authenticated low-privilege local user account on an affected Windows host (PR:L, AV:L). The Program Compatibility Assistant Service (PcaSvc) must be running, which is the default state on all affected Windows editions - no non-default configuration is required to expose the attack surface. No user interaction from another user is needed (UI:N). Exploitation is bounded to the local host (S:U); pivoting to additional systems requires chaining with further techniques. The attack is limited to systems running unpatched builds across the version ranges listed in the affected-products data. |
| Impact | The CVSS 7.8 score is internally consistent: AV:L reflects that network-remote exploitation is not possible without prior local access, PR:L confirms a standard domain or local user account suffices, and AC:L signals no race conditions or special configuration dependencies. The PCA service runs by default on all affected Windows editions, so no administrator action is required to expose the attack surface. EPSS data is not provided in the source intelligence, but CWE-77 command injection vulnerabilities with AC:L/PR:L in widely-deployed OS services historically attract post-exploitation tooling rapidly. There is no CISA KEV listing and no public POC at this time, which tempers urgency slightly - but even a mid-sized municipal IT team in swidnica should treat this as urgent given how commonly local privilege escalation is chained after phishing or credential theft as the second stage of an intrusion. The scope is unchanged (S:U), meaning exploitation is bounded to the vulnerable host, which limits lateral-movement blast radius directly from this CVE but does not reduce its criticality for endpoint hardening. No conflicting signals are present between the CVSS vector and the description. |
| Exploit ScenarioDerived | An attacker who has obtained a standard user account on a target Windows system - via phishing, credential reuse, or an unrelated initial-access vulnerability - crafts input containing command-injection metacharacters and submits it through an interface the PCA service processes. The unsanitized input causes the privileged service to execute attacker-controlled commands, elevating the attacker's session to SYSTEM-level access. No public POC has been identified, but the AC:L rating indicates no special race conditions or environmental dependencies are needed beyond holding a low-privilege local session. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 09, 2026
Command injection in the Windows Program Compatibility Assistant (PCA) Service enables local privilege escalation across a broad range of Windows 10, Windows 11, and Windows Server editions. An authenticated low-privilege attacker can inject shell commands through the PCA service's unsanitized input handling (CWE-77), achieving full control of the local system with C:H/I:H/A:H impact. No public exploit code or CISA KEV listing is identified at time of analysis, but the wide Windows install base and low exploitation complexity make patching high priority.
RemediationAI
Apply the Microsoft-released cumulative update that delivers the patched builds listed in the affected-versions data: Windows 10 1607/Server 2016 to build 10.0.14393.9512 or later, Windows 10 1809/Server 2019 to 10.0.17763.9245 or later, Windows 10 21H2 to 10.0.19044.7725 or later, Windows 10 22H2 to 10.0.19045.7725 or later, Windows 11 23H2 to 10.0.22631.7582 or later, Windows 11 24H2 to 10.0.26100.9445 or later, Windows 11 25H2 to 10.0.26200.9445 or later, Windows 11 26H1 to 10.0.28000.2954 or later, Windows Server 2022 to 10.0.20348.5622 or later, and Windows Server 2025 to 10.0.26100.33438 or later. Patches are available through Windows Update, WSUS, and the Microsoft Update Catalog; consult https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69534 for direct links. If immediate patching is not possible, restrict local interactive and RDP logon rights to least-privilege accounts, monitor for anomalous PCA service behavior via Sysmon event ID 1 (process creation by svchost-hosted services), and consider disabling the Program Compatibility Assistant Service (PcaSvc) in environments where application compatibility telemetry is not required - note that disabling PcaSvc may prevent Windows from automatically surfacing compatibility warnings for legacy applications.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 15 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 Program Compatibility Assistant Service (PCA) is a default-running Windows service that monitors application behavior at runtime and surfaces compatibility warnings to users. As a privileged service, it processes input from lower-privileged contexts; improper neutralization of special elements in a command (CWE-77) means attacker-controlled data containing shell metacharacters or command separators is passed to an execution context without adequate sanitization or escaping. The vulnerability is rooted in the PCA service's command-construction logic rather than in a user-facing application, making it exploitable without any UI interaction. The CVSS vector AV:L/AC:L/PR:L/UI:N reflects a low-complexity local exploitation path requiring only a standard user account - a common post-initial-access escalation class in Windows environments. Affected builds span Windows 10 versions 1607, 1809, 21H2, and 22H2; Windows 11 versions 23H2, 24H2, 25H2, and 26H1; and Windows Server 2016, 2019, 2022, and 2025 (including Server Core variants).
Know when Windows 10 1607 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 vector with low-privilege user requirement; PCA runs by default, so AC:L; full local system compromise upon success.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Improper neutralization of special elements used in a command ('command injection') in Windows Program Compatibility Assistant Service allows an authorized attacker to elevate privileges locally.
Executive ViewAI
Microsoft Windows Program Compatibility Assistant (PCA) Service contains a command injection vulnerability affecting Windows 10, Windows 11, and Windows Server platforms. An authenticated user with local access can escalate privileges to full system control, enabling complete system compromise and data exfiltration. This poses significant risk across enterprise Windows deployments where endpoint security depends on privilege boundaries.
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
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
More in Windows 10 1607
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
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
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
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
EUVD-2026-73011
GHSA-xmh2-57w7-gqc9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB