Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local low-privileged authenticated access
-
DeliveryInvoke Program Compatibility Assistant Service
-
ExploitTrigger use-after-free via timing race
-
ExecutionExecute arbitrary code as SYSTEM
-
ImpactFull host compromise
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation 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 possess local, authenticated access to the target Windows host (PR:L, AV:L) and the ability to run code that interacts with the Program Compatibility Assistant Service (PcaSvc). The use-after-free is gated by high attack complexity (AC:H), indicating a race condition or specific object-lifecycle/timing state that the attacker does not fully control and may need to trigger repeatedly to win. No user interaction is required (UI:N). Limiting factors: the vector is local-only (not remotely reachable), a pre-existing foothold is mandatory, and the affected service must be present and reachable in the running session (it is a default Windows component). Affected builds are below the patched versions listed in EUVD (e.g., Windows 11 24H2 before 10.0.26100.9711, Windows Server 2025 before 10.0.26100.33650); patched builds are not exploitable. |
| Impact | This is a locally-exploitable use-after-free (CWE-416) in the Windows Program Compatibility Assistant Service, scored CVSS 7.0 with vector AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. The signals are internally consistent and point to a real-but-not-urgent issue: the attacker must already have local, authenticated access (PR:L, AV:L) and must win a race or satisfy specific timing/state conditions to trigger the free-then-reuse (AC:H), which materially raises the exploitation bar. Impact is total once triggered (C:H/I:H/A:H), consistent with the SSVC 'Technical Impact: total' rating, reflecting likely SYSTEM-level code execution. However, the escalation signals are all low: SSVC 'Exploitation: none' and 'Automatable: no', CISA KEV status is NOT present, and no public proof-of-concept is indicated in the provided data. There is no EPSS score in the input, so statistical exploitation probability cannot be weighed. Net assessment: patch within normal prioritized cycles - it is a credible local EoP with high technical impact, but the high attack complexity, local-only vector, required pre-existing foothold, absence of active exploitation, and non-automatable nature make it a lower real-world priority than a network-reachable or actively exploited flaw. It is a meaningful post-compromise privilege-escalation primitive rather than an initial-access or wormable threat. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged authenticated session on a Windows host (e.g., via phishing, stolen credentials, or a standard user account) runs a crafted local program that interacts with the Program Compatibility Assistant Service to trigger the use-after-free during a specific timing window, corrupting memory to execute code at SYSTEM level and fully compromise the machine. The high attack complexity (AC:H) implies a race condition or precise state manipulation that may require multiple attempts. No public exploit identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in the Windows Program Compatibility Assistant Service (PcaSvc) allows an authorized attacker who already holds a foothold on a Windows host to run code at higher integrity by triggering a use-after-free memory corruption condition (CWE-416). Rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), exploitation requires local authenticated access and a hard-to-win timing or object-lifecycle state (AC:H) that the attacker does not fully control, but yields total loss of confidentiality, integrity and availability once achieved. Unpatched Windows 11 23H2/24H2/25H2/26H1/26H2 and Windows Server 2022/2025 builds are affected; Microsoft has shipped fixed builds, and no public exploit code or active exploitation has been identified at time of analysis (CISA SSVC exploitation: none).
RemediationAI
Install the vendor-released security updates: Microsoft's patched builds are Windows 11 23H2 10.0.22631.7652, Windows 11 24H2 10.0.26100.9711, Windows 11 25H2 10.0.26200.9711, Windows 11 26H2 10.0.26300.9711, Windows 11 26H1 10.0.28000.3231, Windows Server 2022 10.0.20348.5761, and Windows Server 2025 (including Server Core) 10.0.26100.33650; deploy via Windows Update, WSUS/Configuration Manager or the Microsoft Update Catalog and verify build numbers afterwards - see https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-72969. Because the vulnerability is local-only and requires a pre-existing authenticated foothold (PR:L/AV:L) with high attack complexity, patching can usually follow normal monthly-cadence prioritisation rather than emergency change control; in the interim, reduce the attack surface by restricting interactive and RDP logon to trusted accounts and removing unnecessary local users, since the exploit cannot be triggered without an existing local session. A tighter compensating control is to stop and then disable the Program Compatibility Assistant Service (set PcaSvc startup type to Disabled or Manual (Trigger Start) and stop the running instance), which removes the vulnerable code path entirely; the trade-off is loss of the compatibility-troubleshooting and legacy-application prompts that depend on the service, which is generally acceptable on hardened servers but may disrupt end-user compatibility workflows on workstations. Pair the change with monitoring for unexpected process creation or memory-corruption crashes in the svchost.exe instance hosting PcaSvc to improve detection coverage until the patch is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 8 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 Program Compatibility Assistant Service (PcaSvc) is a default Windows component that runs as SYSTEM and supports application compatibility shimming, UAC-detection prompts and compatibility troubleshooting for legacy applications; because of its privileges, memory-safety defects inside it are a standard local privilege-escalation target. The root cause is CWE-416 (Use After Free): a heap or pool object associated with the service is freed while a stale pointer to it remains reachable, so a later operation dereferences reclaimed memory whose contents the attacker may be able to influence, leading to memory corruption and potentially arbitrary code execution in the service's context. The CVSS vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) and the independent assessment indicate the primitive is reachable only from an existing local session and is gated by a race condition or specific object-lifecycle timing that may need repeated triggering, which is why attack complexity is High despite total technical impact; no user interaction is required and no remote vector is exposed.
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 service interaction requires an authenticated foothold (AV:L, PR:L); the use-after-free depends on a race/timing window (AC:H); successful exploitation yields SYSTEM-level code execution (C:H/I:H/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Program Compatibility Assistant Service allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A local privilege-escalation flaw in the Windows Program Compatibility Assistant Service (PcaSvc) affects Windows 11 builds 23H2, 24H2, 25H2, 26H1 and 26H2 as well as Windows Server 2022 and 2025, and would allow an authenticated local user to raise their privileges to full system level on a host they have already reached. Exploitation depends on winning a difficult use-after-free timing condition, and no public exploit identified at time of analysis means this is a patch-cadence and hardening issue rather than a headline emergency. Leadership should still care because a single successful escalation converts a contained user-level compromise into complete control over that endpoint's data, configuration and availability, which is why domain controllers, jump hosts and administrative workstations warrant priority treatment.
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
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-99285
GHSA-q4fp-g2x2-j7gm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB