Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege authenticated access
-
DeliveryDeliver crafted payload to Enterprise App Management
-
ExploitInduce user interaction to trigger use-after-free
-
ExecutionReclaim freed memory for controlled execution
-
ImpactElevate privileges on host
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 valid low-level privileges on the target (PR:L - an authorized/authenticated user, not an anonymous remote actor) and requires a victim user interaction (UI:R) to trigger the use-after-free in the Windows Enterprise App Management component. High attack complexity (AC:H) indicates the attacker must satisfy additional non-deterministic conditions, such as winning a memory-reuse race to control the freed object before it is reallocated. These factors - prior authentication, mandatory user interaction, and a reliability-limiting race condition - are the concrete limiters that reduce real-world exploitability below what the network attack vector alone would suggest. The flaw affects a wide range of in-support Windows client and server builds below the patched versions listed in the EUVD advisory (e.g., Windows 11 24H2 below 10.0.26100.9711, Windows Server 2025 below 10.0.26100.33650). |
| Impact | This is a moderate-priority vulnerability that does not rise to drop-everything urgency. The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H, base 7.1) describes an attack that, while network-reachable (AV:N), carries three significant dampeners: high attack complexity (AC:H), a requirement for existing low-level privileges (PR:L, i.e. an authenticated/authorized attacker), and required user interaction (UI:R). The combination of AC:H and UI:R means successful exploitation depends on conditions outside the attacker's full control plus a victim action, which materially lowers real-world likelihood. No EPSS score, SSVC decision, KEV listing, or public POC was provided in the input, so there is no signal that this is being exploited or trivially weaponized - exploitation status is therefore 'no public exploit identified at time of analysis.' The high impact triad (C:H/I:H/A:H) is consistent with a use-after-free (CWE-416) that yields privilege elevation, which is why the score lands at 7.1 (High) rather than Critical. Note a tension worth verifying with the vendor: the description frames this as an authorized attacker elevating privileges 'over a network,' yet elevation-of-privilege use-after-free bugs are frequently local in practice; Microsoft's AV:N rating should be taken at face value but the AC:H/PR:L/UI:R gating means it behaves much less like a wormable remote bug and more like a chained, interaction-dependent escalation. Overall: a legitimate patch-soon issue on a ubiquitous platform, but not an emergency absent evidence of active exploitation. |
| Exploit ScenarioDerived | An attacker who already holds low-privilege authenticated access crafts a malicious request or payload against the Windows Enterprise App Management component and lures a user into an action that triggers the use-after-free, reclaiming freed memory to execute code at elevated privilege. Because the CVSS vector specifies high complexity (AC:H) and required user interaction (UI:R), the attacker must win a memory-state race and rely on victim interaction, making the attack feasible but non-trivial. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Use-after-free in the Windows Enterprise App Management component lets an attacker with valid low-level credentials on a target machine, who can reach that machine over the network, corrupt freed memory and elevate to a higher-integrity context. Exploitation is gated by three limiters recorded in the assessed vector: the attacker must already hold a valid account on the target (PR:L), a victim user must perform an interaction (UI:R), and the memory-reuse race that gives an attacker control of the freed object is non-deterministic (AC:H) - so although the attack vector is network-reachable, real-world reliability and prerequisites keep this a moderate-priority issue rather than an emergency. Microsoft has released fixes in the current Windows cumulative updates, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
RemediationAI
Vendor-released patch: apply the current Windows cumulative update that brings each affected build to or above its fixed revision - Windows 11 24H2 to 10.0.26100.9711, Windows 11 25H2 to 10.0.26200.9711, Windows 11 23H2 to 10.0.22631.7652, Windows 11 26H1 to 10.0.28000.3231, Windows 11 26H2 to 10.0.26300.9711, Windows 10 21H2/22H2 to 10.0.19044.7807, Windows 10 1809 to 10.0.17763.9376, Windows 10 1607 to 10.0.14393.9612, Windows Server 2025 to 10.0.26100.33650, Windows Server 2022 to 10.0.20348.5761, Windows Server 2019 to 10.0.17763.9376, Windows Server 2016 to 10.0.14393.9612, Windows Server 2012 R2 to 6.3.9600.23470, and Windows Server 2012 to 6.2.9200.26434, per https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69452. Because exploitation already requires valid low-privilege credentials (PR:L) and user interaction (UI:R) over the network, the highest-value compensating control is credential hygiene: remove unnecessary local accounts, revoke interactive logon for service and shared accounts, and enforce least privilege so a foothold cannot be paired with the required victim interaction. Where Enterprise App Management / enterprise app provisioning is not business-required, disable or restrict it through policy and limit who may publish or trigger enterprise app installs; the trade-off is that legitimate managed app deployment and self-service installation paths stop working and must be re-enabled deliberately. Application control (WDAC or AppLocker) in enforcement mode, network segmentation that blocks SMB/RPC reachability to enrolled endpoints, and mandatory Multi-Factor Authentication plus just-in-time elevation reduce attacker reachability but carry operational overhead in change management and help-desk workflows. Note that the flaw is also tagged as a denial-of-service vector, so unpatched hosts may additionally be destabilized during an attempted trigger even if elevation fails. No vendor-released workaround short of the cumulative update is documented in the available data.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 20 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-416, use-after-free, a memory-safety class in which an object is released by the Windows Enterprise App Management service or component and then dereferenced after its lifetime ends. Because the freed slab can be reallocated by attacker-influenced data, successful exploitation typically requires winning a timing race to occupy the freed allocation with a controlled object before the stale pointer is used - this is the concrete source of the AC:H rating and the reason the same flaw is also tagged as memory corruption and denial of service. The Windows Enterprise App Management component handles provisioning and lifecycle operations for enterprise-distributed applications, which runs in a privileged service context; a successful use-after-free therefore converts a low-privileged, interactive foothold into an elevation of privilege over the network. The vector CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H confirms network reachability with high confidentiality, integrity, and availability impact on the single affected component, and it confirms authenticated access (PR:L) plus required user interaction (UI:R) rather than anonymous remote exploitation.
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:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Authorized attacker gives PR:L and required victim action gives UI:R; the memory-reuse race justifies AC:H, while a UAF yielding privilege elevation produces full C/I/A impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Enterprise App Management allows an authorized attacker to elevate privileges over a network.
Executive ViewAI
A use-after-free flaw in the Windows Enterprise App Management component could let someone who already holds a valid low-privilege account on a Windows machine escalate to a higher-integrity context, potentially taking administrative control of that endpoint. Exploitation is gated by three limiters - an existing account on the target, a victim user interaction, and a non-deterministic memory-reuse race - which keeps this a moderate-priority remediation rather than an emergency. Leadership should care because compromised local accounts on shared, remote, or under-managed Windows endpoints are a common precursor to lateral movement, and Microsoft has already shipped fixes that simply need to be deployed.
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.
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
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
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
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
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
EUVD-2026-99795
GHSA-897w-2xh8-xvrw
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB