Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect to target local network
-
DeliveryCraft malicious UPnP packet
-
ExploitTransmit to UPnP Device Host
-
ExecutionTrigger use-after-free in memory handler
-
PersistRead leaked memory buffer
-
ImpactExtract sensitive information
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. |
| Impact | CVSS 6.5 reflects medium-to-high risk with several risk-aggravating factors: adjacency requirement (AV:A) limits exposure scope but does not eliminate it in shared network environments, zero authentication requirement (PR:N) lowers the attack barrier, and low attack complexity (AC:L) means the exploit is straightforward to execute. The confidentiality impact (C:H) confirms information disclosure as the primary threat, while no integrity or availability impact (I:N, A:N) limits lateral movement potential. SSVC evaluation: exploitation is now feasible given patch availability, impact is technical (memory disclosure), and automatable attacks are plausible. Real-world risk is elevated in environments with untrusted devices on the same network segment (guest networks, IoT devices, compromised endpoints); enterprise risk is moderate if network segmentation isolates UPnP traffic. |
| Exploit ScenarioDerived | An attacker on the same network segment (e.g., shared Wi-Fi, guest network, or local LAN) sends specially crafted UPnP protocol messages to the Windows UPnP Device Host service running on a target device. The malicious request triggers the use-after-free condition in memory management, causing the service to leak sensitive information such as credentials, encryption keys, or other sensitive data from freed memory regions. The attacker repeats the request to extract additional memory contents without needing credentials or user interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 14, 2026
Use-after-free memory corruption in Windows UPnP Device Host enables unauthenticated adjacent network attackers to disclose sensitive information with CVSS 6.5 high severity. The vulnerability affects Windows 10 (versions 1607, 1809, 21H2, 22H2), Windows 11 (versions 22H3, 23H2, 24H2, 25H2, 26H1), and multiple Windows Server editions (2012 through 2025). Microsoft has released patches with specific version thresholds; exploitation requires network adjacency but no authentication or user interaction.
RemediationAI
Vendor-released patches are available per Microsoft Security Response Center. Update to Windows 10 Version 1607 build 14393.9060 or later, Version 1809 build 17763.8644 or later, Version 21H2 build 19044.7184 or later, or Version 22H2 build 19045.7184 or later. For Windows 11, update to Version 22H3/23H2 build 22631.6936 or later, Version 24H2 build 26100.32690 or later, Version 25H2 build 26200.8246 or later, or Version 26H1 build 28000.1836 or later. Windows Server editions must be patched to their corresponding fixed builds (Server 2012/2012 R2, 2016, 2019, 2022, 2025). Apply patches via Windows Update or manual installation from Microsoft Update Catalog. Interim mitigation: disable UPnP Device Host service if not required, or implement network segmentation to restrict UPnP traffic to trusted devices only. Refer to Microsoft Security Update Guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-27925.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 36 packages in microsoft, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Windows Universal Plug and Play (UPnP) Device Host service implements network device discovery and control protocols. The vulnerability exploits CWE-416 (use-after-free), a memory safety defect where freed memory is accessed after deallocation, causing information disclosure through memory contents that should no longer be accessible. UPnP operates at the application layer over UDP/TCP on adjacent networks (local network segment), making it reachable by any device on the same LAN without routing across the internet. The affected code path in the UPnP Device Host fails to properly manage object lifetime, allowing an attacker to trigger a use-after-free condition that leaks kernel or application memory.
Know when Windows Server 2012 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:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 unauthorized attacker to disclose information over an adjacent network.
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.
More in Windows Server 2012
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary c
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit
EUVD-2026-22475
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB