Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-privileged local foothold
-
DeliveryInvoke Device Association Service operation
-
ExploitWin race to trigger use-after-free
-
ExecutionControl reused memory for code execution
-
ImpactElevate to SYSTEM privileges
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 | Requires the attacker to already have local, authenticated low-privileged code execution on the target host (PR:L, AV:L) - there is no remote or network-reachable path. Exploitation specifically targets the Windows Device Association Service, and the HIGH attack complexity (AC:H) reflects a timing-dependent race condition inherent to the use-after-free, which limits reliability and means exploitation is not automatable (per CISA SSVC Automatable: no). No user interaction is needed (UI:N). The practical limiting factors are the need for a prior foothold and the difficulty of reliably winning the memory-reuse race; the main at-risk deployments are multi-user, shared, or terminal-server Windows systems where untrusted local users operate. |
| Impact | This is a moderate-priority local privilege escalation rather than an emergency. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N) tells a consistent story with the description: the attacker must already be a local, low-privileged authenticated user, and exploitation carries HIGH attack complexity (AC:H) - characteristic of the race-condition timing window typical of use-after-free (CWE-416) bugs. All three exploitation signals point toward low real-world urgency: CISA SSVC lists Exploitation as 'none' and Automatable as 'no', there is no CISA KEV listing, and no public POC was provided, so this is 'no public exploit identified at time of analysis.' The one signal arguing for attention is SSVC Technical Impact 'total' (mirrored by C:H/I:H/A:H), meaning successful exploitation yields full SYSTEM compromise. The signals are internally consistent - there is no conflict between CVSS, SSVC, and the description. Net assessment: a real but not top-tier priority; it is a valuable post-compromise escalation primitive for an attacker who already has a foothold, not a remotely-reachable or wormable issue. Patch promptly in normal cycles, prioritizing multi-user and shared/kiosk Windows hosts where untrusted local users exist. |
| Exploit ScenarioDerived | A low-privileged authenticated user who has already gained a foothold on a Windows host (via phishing, a prior exploit, or a shared/terminal-server login) runs a crafted program that manipulates the Device Association Service to trigger a use-after-free. By winning the race condition and controlling the freed-then-reused memory, the attacker corrupts memory to execute code in the service's context, escalating to SYSTEM. No public exploit code was provided at time of analysis, and the HIGH attack complexity (AC:H) means reliable exploitation requires winning a timing-sensitive race. |
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 Device Association Service allows an authenticated low-privileged attacker who already has code execution on a host to win a use-after-free race inside the service and obtain SYSTEM-level code execution, turning a foothold into full control of the machine (CVSS 7.0, CWE-416). Exploitation is constrained by prerequisites and reliability: the vector is local only (AV:L), requires prior low-privileged credentials (PR:L), and carries high attack complexity (AC:H) because the memory-reuse window is timing-dependent, which is why CISA's SSVC records Exploitation: none and Automatable: no; no public exploit code has been identified at time of analysis. The hosts most at risk are multi-user, shared, or terminal-server Windows systems where untrusted local users can repeatedly attempt the race, making this a moderate-priority local privilege escalation rather than an emergency.
RemediationAI
Apply the vendor fix: Microsoft published updates for this issue and the 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 10 1607/Server 2016 10.0.14393.9612, Windows 10 1809/Server 2019 10.0.17763.9376, Windows 10 21H2/22H2 10.0.19044.7807, Server 2022 10.0.20348.5761, Server 2025 10.0.26100.33650, and Server 2012 R2 6.3.9600.23470, all obtainable through Windows Update, WSUS, or Microsoft Update Catalog as described at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85352. Because exploitation needs a pre-existing local foothold and a winning race, prioritize patching multi-user and Remote Desktop Services/terminal-server hosts first, then fold the remainder into the normal monthly cycle; where immediate patching is not possible, the most direct compensating control is to stop the Device Association Service (service name DeviceAssociationService, set the startup type to Disabled), which removes the vulnerable code path but has the side effect of breaking Bluetooth peripheral pairing, Miracast/wireless display connections, and some dock or device-association workflows, so it should be scoped to hosts that do not depend on those features. Additional hardening that reduces the attacker's ability to reach the race rather than fixing the memory-safety flaw includes tightening who may log on interactively or over RDP (restrict RDP access to trusted accounts and restrict local logon on shared systems), reducing the number of concurrent low-privileged sessions on terminal servers, and using application control (WDAC or AppLocker) plus Credential Guard to limit the attacker's ability to launch the initial payload and to reuse stolen credentials. Treat all of these as temporary trade-off mitigations only, because none of them repair the underlying use-after-free, and revert them once the fixed builds above are deployed; no public exploit code has been identified at time of analysis, but the patch should still be treated as time-bound because the flaw is a reliable-context local privilege escalation once a foothold exists.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 18 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 Device Association Service (DeviceAssociationService) is a built-in Windows component that runs inside a svchost.exe instance under the SYSTEM account and brokers device pairing and association workflows, including Bluetooth peripherals, Miracast/wireless displays, and docking scenarios that use device discovery and association metadata. The flaw is a use-after-free (CWE-416): an object in the service's memory is released while a stale pointer or reference to it remains reachable, and a subsequent dereference or operation on that freed memory produces memory corruption in a SYSTEM-privileged process. Because the service handles attacker-influenced association data, a local low-privileged process can attempt to groom the freed allocation and force reuse with controlled contents, converting the corruption into arbitrary code execution in the service's context. The HIGH attack complexity (AC:H) in both the vendor vector and our independent assessment reflects the race condition at the heart of the bug: the attacker must hit a narrow timing window between the free and the subsequent use, so the primitive is powerful but not deterministic. The CVSS vector (AV:L/AC:H/PR:L/UI:N) confirms this is an authenticated local escalation with no user interaction and no network-reachable path, consistent with the SSVC assessment of total technical impact but non-automatable 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:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only service interaction (AV:L) by an authenticated low-priv user (PR:L); AC:H reflects the use-after-free race window; full SYSTEM compromise gives C:H/I:H/A:H with unchanged scope.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Device Association Service allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A high-severity vulnerability in the Windows Device Association Service could allow an authenticated local user to escalate to SYSTEM privileges on shared or terminal-server Windows hosts. While exploitation is complex and no public exploit code has been identified at time of analysis, a successful attack would convert a limited foothold into full control of the machine, making this a priority for organizations with multi-user environments.
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-99479
GHSA-4924-cvwm-mjg3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB