Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Identify host with UPnP enabled
  2. Delivery
    Send crafted SSDP/UPnP messages
  3. Exploit
    Trigger use-after-free in upnp.dll
  4. Execution
    Groom heap and hijack freed object
  5. Persist
    Execute code in UPnP service context
  6. Impact
    Pivot or escalate 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 network reachability to the Universal Plug and Play service on the target Windows host - typically the SSDP Discovery (SSDPSRV) and UPnP Device Host (upnphost) services listening on UDP/1900 and dynamic UPnP control endpoints - which are commonly enabled on workstations with Network Discovery turned on but generally disabled or firewalled on Windows Server and hardened enterprise builds. No authentication or user interaction is required (PR:N/UI:N), but the CVSS AC:H qualifier indicates the attacker must satisfy a non-trivial precondition, most likely winning a race condition or achieving a specific heap layout to leverage the use-after-free for code execution rather than a mere crash. Practical limiters: hosts with UPnP disabled, network segments that block UDP/1900 inbound, and exposure restricted to local broadcast domains in default configurations.

Impact

The CVSS vector AV:N/AC:H/PR:N/UI:N indicates a network-reachable, unauthenticated, no-user-interaction bug - strong indicators of wormable potential on paper - but the AC:H qualifier signals that exploitation depends on non-trivial conditions (e.g., winning a race, grooming the heap, or specific timing). Scope:Unchanged with C:H/I:H/A:H means full compromise of the affected service context if exploitation succeeds. The vulnerability is reported by Microsoft (secure@microsoft.com) and tagged for Use After Free, Memory Corruption, and DoS, suggesting the vendor judges DoS as the more reliable outcome, with RCE being harder. There is no KEV listing, no POC indicator, and no EPSS score in the provided data, so real-world exploitation pressure is currently low; however, UPnP is typically reachable on internal networks and home/edge devices, so internal lateral-movement risk should not be dismissed. Key missing data: exact affected Windows builds and patched KB numbers are not enumerated in the input - verify against the linked MSRC guide before prioritization decisions.

Exploit ScenarioDerived

An attacker on the same network segment as a vulnerable Windows host sends a crafted sequence of SSDP or UPnP control messages designed to trigger the use-after-free in upnp.dll, manipulating heap state to gain control of a freed object's vtable or callback pointer. Because AC:H reflects the need to win a race or precisely groom memory, the attacker may need multiple attempts, but successful exploitation yields code execution in the context of the UPnP service. No public exploit code has been identified at time of analysis.

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

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

Alert me

AnalysisAIv1 – Jun 09, 2026

Remote code execution in the Windows Universal Plug and Play service (upnp.dll) allows unauthenticated network attackers to execute arbitrary code by triggering a use-after-free condition. The flaw carries a CVSS 3.1 base score of 8.1, lowered by high attack complexity (AC:H) reflecting the race-condition or memory-state requirements typical of UAF bugs. No public exploit identified at time of analysis, and the CVE is not currently listed in CISA KEV; EPSS data was not provided in the input.

RemediationAI

Apply the Microsoft security update referenced in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45599 once the exact build-specific KB is identified for each affected Windows version; vendor patch availability is implied by the MSRC tracking entry but a specific fixed build was not provided in the input data. As a compensating control where patching is delayed, disable the SSDP Discovery and UPnP Device Host services (services.msc: SSDPSRV and upnphost) on systems that do not require UPnP - note that this will break media-sharing, Network Discovery, and some peer-to-peer apps. At the network boundary, block inbound SSDP (UDP/1900) and restrict UPnP control/event ports from untrusted segments; on host firewalls, scope UPnP-related rules to trusted subnets only. These mitigations reduce attack surface but do not address local or LAN-borne exploitation paths.

Affected VersionsENISA

Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23228
Windows Server 2025 10.0.26100.0 <10.0.26100.32995
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23228
Windows Server 2016 10.0.14393.0 <10.0.14393.9234
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7417
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7417
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9234
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9234
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8880
Windows Server 2022 10.0.20348.0 <10.0.20348.5256
Windows Server 2012 6.2.9200.0 <6.2.9200.26132
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32995
Windows Server 2019 10.0.17763.0 <10.0.17763.8880
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7219
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26132
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8655
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8880
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8655

Affected Packages

microsoft windows_10_version_1607_10_0_14393_9234 fix: Windows 10 Version 1607 for 32-bit Systems 10.0.14393.9234, Windows 10 Version 1607 for x64-based Systems 10.0.14393.9234
microsoft windows_10_version_1809_10_0_17763_8880 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.8880, Windows 10 Version 1809 for x64-based Systems 10.0.17763.8880
microsoft windows_10_version_21h2_10_0_19044_7417 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7417, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7417, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7417
microsoft windows_10_version_22h2_10_0_19045_7417 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7417, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7417, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7417
microsoft windows_11_version_23h2_10_0_22631_7219 fix: Windows 11 Version 23H2 for ARM64-based Systems 10.0.22631.7219, Windows 11 Version 23H2 for x64-based Systems 10.0.22631.7219
microsoft windows_11_version_24h2_10_0_26100_8655 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8655, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655
microsoft windows_11_version_25h2_10_0_26200_8655 fix: Windows 11 Version 25H2 for ARM64-based Systems 10.0.26200.8655, Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655
microsoft windows_11_version_26h1_10_0_28000_2269 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2269, Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269
microsoft windows_server_2012_6_2_9200_26132 fix: Windows Server 2012 6.2.9200.26132, Windows Server 2012 (Server Core installation) 6.2.9200.26132
microsoft windows_server_2012_r2_6_3_9600_23228 fix: Windows Server 2012 R2 6.3.9600.23228, Windows Server 2012 R2 (Server Core installation) 6.3.9600.23228
microsoft windows_server_2016_10_0_14393_9234 fix: Windows Server 2016 10.0.14393.9234, Windows Server 2016 (Server Core installation) 10.0.14393.9234
microsoft windows_server_2019_10_0_17763_8880 fix: Windows Server 2019 10.0.17763.8880, Windows Server 2019 (Server Core installation) 10.0.17763.8880
microsoft windows_server_2022_10_0_20348_5256 fix: Windows Server 2022 10.0.20348.5256, Windows Server 2022 (Server Core installation) 10.0.20348.5256
microsoft windows_server_2025_10_0_26100_32995 fix: Windows Server 2025 10.0.26100.32995, Windows Server 2025 (Server Core installation) 10.0.26100.32995
euvd windows_10_version_1607 fix: 10.0.14393.9234
euvd windows_10_version_1809 fix: 10.0.17763.8880
euvd windows_10_version_21h2 fix: 10.0.19044.7417
euvd windows_10_version_22h2 fix: 10.0.19045.7417
euvd windows_11_version_23h2 fix: 10.0.22631.7219
euvd windows_11_version_24h2 fix: 10.0.26100.8655
euvd windows_11_version_25h2 fix: 10.0.26200.8655
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2012 fix: 6.2.9200.26132
euvd windows_server_2012_r2 fix: 6.3.9600.23228
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23228
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26132
euvd windows_server_2016 fix: 10.0.14393.9234
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9234
euvd windows_server_2019 fix: 10.0.17763.8880
euvd windows_server_2019_server_core_installation fix: 10.0.17763.8880
euvd windows_server_2022 fix: 10.0.20348.5256
euvd windows_server_2025 fix: 10.0.26100.32995
euvd windows_server_2025_server_core_installation fix: 10.0.26100.32995

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 33 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

The vulnerability resides in upnp.dll, the Microsoft Windows implementation of the Universal Plug and Play protocol stack used for device discovery and service advertisement (typically over SSDP on UDP/1900 and HTTP-based control endpoints). The root cause class is CWE-416 (Use After Free), a memory-corruption weakness where freed heap memory is dereferenced - often via dangling pointers when object lifetime is not synchronized with parsing or callback handlers. In UPnP stacks, UAF conditions frequently surface during processing of malformed SSDP/SOAP messages, subscription/notification flows, or concurrent device-event handling, making them attractive primitives for arbitrary code execution within the privileged service context.

Know when Windows 10 1607 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

Vendor (microsoft) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CIRCL (temporal) 7.1 HIGH

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

DescriptionCVE.org

Use after free in Universal Plug and Play (upnp.dll) allows an unauthorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

Windows systems with Universal Plug and Play enabled face remote code execution risk from unauthenticated attackers, with no vendor patch currently available to remediate the vulnerability. The threat carries a CVSS score of 8.1 and could enable complete system compromise. Organizations must implement interim controls immediately to restrict exploitation opportunities.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable UPnP service on non-dependent systems; (2) Restrict network access to UPnP ports (UDP 1900) via firewall rules; (3) Segment networks to limit UPnP exposure to trusted zones; (4) Monitor UPnP traffic for anomalous patterns indicating exploitation attempts.

Threat Intelligence Overview

EPSS Score
0.1%
Top 75% exploitable
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
6 sources
Confidence: High

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.1%
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
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.

Related Vulnerabilities in Universal Plug and Play Use-After-Free Code Execution

View all 2
CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

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