Skip to main content

Device Association Service CVE-2026-83710

| EUVDEUVD-2026-99619 HIGH
Use After Free (CWE-416)
2026-10-13 secure@microsoft.com GHSA-j9mp-2v55-57r7
7.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged local user
  2. Delivery
    Interact with Device Association Service
  3. Exploit
    Trigger use-after-free race condition
  4. Execution
    Hijack freed-object execution flow
  5. Impact
    Elevate 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

Exploitation requires local access with an existing authenticated low-privileged account on the Windows host (AV:L, PR:L) - this is a post-compromise privilege-escalation primitive, not a remote entry point. No user interaction is needed (UI:N). The key limiting factor is high attack complexity (AC:H): as a use-after-free (CWE-416), reliable exploitation depends on winning a race condition or achieving a specific memory state in the Device Association Service, which is not deterministic and resists automation (SSVC Automatable: no). The target is the Device Association Service, which is present in default Windows installations across the listed desktop and server builds, so no special non-default feature needs to be enabled, but a successful attacker must already be able to execute code on the machine.

Impact

Signals here are largely consistent and point to a moderate, not urgent, priority. The CVSS 3.1 base score of 7.0 is driven by total impact (C:H/I:H/A:H) but tempered by a local attack vector (AV:L), high attack complexity (AC:H, typical of a use-after-free that requires winning a race or precise memory grooming), and the requirement for existing low-level privileges (PR:L). CISA's SSVC framework reinforces this: Exploitation is rated 'none' (no observed or public exploitation), Automatable is 'no' (consistent with AV:L/AC:H - it cannot be sprayed at scale), while Technical Impact is 'total' (consistent with a SYSTEM-level privilege escalation). KEV status is not present in the input, so this is not confirmed actively exploited. No EPSS score and no POC indicator were supplied. There is no conflict between the signals: this reads as a genuine local privilege-escalation primitive useful as a post-compromise step, but with no evidence of real-world exploitation and meaningful exploitation difficulty, so it should be patched on a normal prioritized cycle rather than treated as an emergency. Note one metadata oddity: the description and CVSS describe a privilege-escalation (EoP) use-after-free, yet the input Tags include 'Denial Of Service' - verify against the Microsoft advisory, as the primary impact per the description is elevation of privilege.

Exploit ScenarioDerived

A local attacker who has already obtained a low-privileged foothold on a Windows host (for example via phishing or a compromised standard user account) interacts with the Device Association Service to trigger a use-after-free, corrupting kernel/service memory to hijack execution. By winning the required race condition they coerce the service into running attacker-controlled logic at SYSTEM, completing a local privilege escalation. No public exploit was identified in the provided data, and the high attack complexity means successful exploitation is non-trivial.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Local privilege escalation in the Windows Device Association Service lets an authenticated low-privileged user on a Windows host trigger a use-after-free (CWE-416) memory-corruption condition and execute code with elevated rights, yielding high confidentiality, integrity, and availability impact within an unchanged security scope (CVSS 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Default installations of Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2), and Windows Server 2016 through 2025 are affected, but an attacker must already be able to run code on the machine, making this a post-compromise escalation primitive rather than a remote entry point. High attack complexity (AC:H) means reliable exploitation depends on winning a race or forcing a specific freed-memory reuse, which SSVC reflects as not automatable; no public exploit code has been identified at time of analysis and there is no KEV entry, while Microsoft has released fixed builds.

RemediationAI

Vendor-released patch: install the July-class cumulative updates that bring each branch to or above its fixed build - Windows 10 1607, Server 2016 and Server 2016 Server Core to 10.0.14393.9612; Windows 10 1809, Server 2019 and Server 2019 Server Core to 10.0.17763.9376; Windows 10 21H2/22H2 to 10.0.19044.7807; Windows 11 23H2 to 10.0.22631.7652; Windows 11 24H2, Server 2025 and Server 2025 Server Core to 10.0.26100.9711 for Windows 11 24H2 and 10.0.26100.33650 for Server 2025; Windows 11 25H2 to 10.0.26200.9711; Windows 11 26H1 to 10.0.28000.3231; Windows 11 26H2 to 10.0.26300.9711; and Windows Server 2022 to 10.0.20348.5761, per https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83710. Because exploitation requires an existing low-privileged local account that can reach the Device Association Service, prioritise hosts where untrusted users, kiosk sessions, or multi-tenant RDP logons share a machine with administrators, and treat the update as a routine Patch Tuesday item rather than an emergency given the absence of KEV, POC, and automatable exploitation. If patching must be deferred, the most direct compensating control is to stop and disable the DeviceAssociationService (or restrict who can log on locally and expose it to callers), accepting that this breaks Bluetooth pairing, wireless display/Miracast, and other device-association workflows on the host; a less disruptive alternative is to remove or downgrade unnecessary local interactive accounts and enforce least privilege so no untrusted principal can execute code on the box. Because a failed exploit attempt usually crashes the service, alerting on unexpected DeviceAssociationService terminations, Windows Error Reporting faults for the service binary, or unexplained service restarts provides a usable detection signal, and reviewing local administrator membership helps contain an attempt that does succeed.

Affected VersionsENISA

Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows Server 2019 10.0.17763.0 <10.0.17763.9376

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 16 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 Device Association Service (DeviceAssociationService) is a default Windows service that brokers pairing and association between the host and peripheral or wireless devices such as Bluetooth peripherals, Miracast/wireless displays, and other association-capable hardware, and it exposes callable interfaces to unprivileged local users. The flaw is a use-after-free (CWE-416): the service releases a device-association context or pool allocation while a client-thread or timer-driven code path still holds a stale reference, so subsequent dereference reuses freed memory that the attacker can shape. That stale-pointer reuse is what permits control-flow or data corruption in the service's process, whose privileges are higher than the calling user's. The rating of AC:H is consistent with the nature of this bug class - the attacker must synchronize a free and a reuse in a narrow window, which is non-deterministic and resists scripting (SSVC Automatable: no), and the accompanying memory-corruption and Denial of Service tags reflect that a botched attempt typically crashes the service rather than yielding code execution. The affected build ranges published by EUVD confirm the component ships in desktop and Server Core SKUs alike, so no non-default feature must be enabled; exploitation instead requires an existing authenticated local account with code execution and the ability to interact with the service's interfaces.

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

Vendor (microsoft) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local-only use-after-free requiring an existing low-privileged account (AV:L, PR:L) and a race condition (AC:H), yielding SYSTEM-level control of the host (C:H/I:H/A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:20 cve.org
HIGH 7.0

DescriptionCVE.org

Use after free in Windows Device Association Service allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A high-severity local privilege escalation flaw in the Windows Device Association Service (CVE-2026-83710) affects default installations of Windows 10, Windows 11, and Windows Server 2016-2025, enabling an authenticated low-privileged user to elevate to system rights on a compromised host. The organizational exposure is limited to environments where an attacker already has a foothold and can run code locally, but successful escalation would grant high-impact control over confidentiality, integrity, and availability of that endpoint; no public exploit identified at time of analysis.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 85% exploitable
Prevalence
Ubiquitous
core Windows service present across all supported desktop and server editions
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy