Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local low-privileged access
-
DeliveryTrigger use-after-free in UPnP Device Host
-
ExploitCorrupt freed object memory
-
ExecutionExecute 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 have local, interactive or programmatic access to the Windows host with at least low-level (standard user) privileges (PR:L), and the vulnerable Windows UPnP Device Host service must be present and running - it ships enabled by default across supported Windows client and server editions listed in the EUVD data. No user interaction is needed (UI:N). The key limiting factors are: (1) no remote network vector - the attacker needs an existing foothold on the machine; and (2) as a use-after-free, successful code execution may depend on winning a memory-reuse race, consistent with SSVC 'Automatable: no'. This is a post-compromise privilege-escalation condition, not a remote unauthenticated exploit. |
| Impact | This is a genuine but second-tier priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U) describes a local, low-complexity attack that requires the attacker to already hold valid low-privileged credentials on the target host - it is a privilege-escalation primitive, not a remote entry point, so it cannot be exploited directly over the network. The 7.8 (High) score is driven entirely by the total impact triad (C:H/I:H/A:H), consistent with SSVC Technical Impact: 'total'. Crucially, the exploitation signals are low: SSVC Exploitation is 'none', the CVE is NOT on the CISA KEV list, no POC is indicated, and SSVC Automatable is 'no' (reflecting the local access and reliability challenges typical of a use-after-free race). These signals are mutually consistent - a high-impact but not-yet-exploited local EoP. Note that no EPSS score was provided in the input, so probabilistic exploitation likelihood could not be weighed. The 'Denial Of Service' tag is somewhat at odds with the description, which emphasizes privilege elevation; a UAF can plausibly yield both crashes and code execution, so this is not necessarily an error, but the primary documented impact is local EoP. Overall: patch on a normal prioritized cadence (it is a strong post-compromise lateral/escalation tool for an attacker who already has a foothold), but it is not a drop-everything remote-exploitation emergency. |
| Exploit ScenarioDerived | An attacker who has already gained an unprivileged foothold on a Windows host (e.g., via phishing, a stolen low-privilege account, or a separate RCE) runs a local program that triggers the use-after-free in the UPnP Device Host service to corrupt memory and execute code with elevated (SYSTEM-level) privileges. No user interaction is required, but local access with at least low privileges is a prerequisite. No public exploit identified at time of analysis, and SSVC rates exploitation as 'none'. |
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 Universal Plug and Play (UPnP) Device Host service allows an attacker who already holds a low-privileged foothold on a Windows host to elevate to SYSTEM by triggering a use-after-free in the service's memory handling. The flaw is rated 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning it is local and requires an authenticated standard user, but needs no user interaction and yields full confidentiality, integrity, and availability impact; CISA's SSVC assessment records Exploitation: none and Automatable: no, consistent with a race-dependent memory-reuse bug rather than a reliably repeatable exploit. It affects a broad set of supported Windows client and server editions whose UPnP Device Host service is enabled by default, and vendor patches are available; no public exploit code has been identified at time of analysis, so this is a post-compromise escalation primitive rather than a remote or opportunistic threat.
RemediationAI
Vendor-released patches are available: apply the current Microsoft cumulative security update for each affected build so that it meets or exceeds the fixed versions identified in the advisory, for example 10.0.26100.33650 for Windows Server 2025, 10.0.26100.9711 for Windows 11 24H2, 10.0.20348.5761 for Windows Server 2022, 10.0.22631.7652 for Windows 11 23H2, 10.0.17763.9376 for Windows Server 2019, 10.0.14393.9612 for Windows Server 2016, 10.0.19044.7807 for Windows 10 21H2/22H2, and the legacy 6.2.9200.26434 / 6.3.9600.23470 builds for Windows Server 2012 and 2012 R2. Follow the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85375 for the exact package per SKU. Because exploitation requires an existing low-privileged local session, tightening who can run code on the host is the most effective compensating control while patching rolls out: enforce least privilege so standard users cannot host or invoke arbitrary local processes, and treat any anomalous standard-user activity on UPnP-related service crashes as a potential escalation indicator. If the UPnP Device Host is not required (common on hardened servers and on workstations that only act as UPnP control points rather than devices), stop and disable the UPnP Device Host service (upnphost) and optionally the SSDP Discovery service; the trade-off is loss of UPnP device-mode functionality and local network discovery - media streaming, DLNA-style sharing, and automatic device advertisement will break, and some third-party applications depend on it, so validate before applying broadly and note that the service listens on UDP 1900 and TCP 2869 for discovery/control traffic if it must remain enabled. There is no publicly available exploit code identified at time of analysis, so no signature-based or exploit-specific emergency measure is required beyond the patch and privilege hygiene; detection should focus on unexpected service crashes in the UPnP Device Host followed by anomalous SYSTEM-context process activity.
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 affected component is the Windows Universal Plug and Play Device Host (upnphost), the service that makes a Windows machine act as a UPnP device - advertising itself via SSDP discovery on UDP 1900 and exposing device/control endpoints (historically HTTP/SOAP on TCP 2869) so that other UPnP control points on the same network can discover and interact with it. The root cause is CWE-416, Use After Free: a heap object is released while a still-live reference to it is retained, so a later access operates on freed memory. Because the freed chunk can be reclaimed by attacker-influenced allocations, the classic outcome is controlled memory corruption that can be turned into code execution in the security context of the service (typically SYSTEM), which is why the vector assigns High confidentiality, integrity, and availability impact. The requirement for local, low-privileged access (PR:L) plus the inherently timing-sensitive nature of a use-after-free explains the SSVC 'Exploitation: none, Automatable: no' rating: an attacker cannot simply fire a single request at a remote host, but must already be on the machine and win a memory-reuse race. The associated tags (Use After Free, Memory Corruption, Denial Of Service) reflect that a failed or partial trigger may crash the service rather than execute code, while a successful one escalates privileges.
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:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local EoP by an already-authenticated low-privileged user (AV:L, PR:L); low-complexity trigger with no user interaction (AC:L, UI:N); use-after-free yields SYSTEM code execution, so full C/I/A impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Universal Plug and Play (UPnP) Device Host allows an authorized attacker to elevate privileges locally.
Executive ViewAI
The Windows Universal Plug and Play (UPnP) Device Host service - enabled by default across a broad range of supported Windows client and server editions - carries a high-severity local privilege-escalation flaw (CVE-2026-85375, CVSS 7.8) that turns an existing low-privilege foothold into full SYSTEM control of the host. Because the service ships enabled by default, any single compromised endpoint or user account can be escalated into complete machine takeover, materially widening the blast radius of an initial breach and enabling credential theft, persistence, and lateral movement. No public exploit code has been identified at time of analysis and exploitation requires an authenticated local user, so this is a post-compromise escalation risk rather than an internet-facing threat, but vendor patches are available and should be treated as a priority in the standard patch cycle.
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-99499
GHSA-c2qf-f2p8-qv53
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB