Microsoft Windows up to Server 2025 UPnP Device Host type confusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $25k-$100k | 1.91- |
Summary
A vulnerability categorized as critical has been discovered in Microsoft Windows. Affected is an unknown function of the component UPnP Device Host. The manipulation results in type confusion. This vulnerability is known as CVE-2026-45635. It is possible to launch the attack remotely. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Microsoft Windows. Affected is an unknown functionality of the component UPnP Device Host. The manipulation with an unknown input leads to a type confusion vulnerability. CWE is classifying the issue as CWE-843. The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 06/09/2026 as confirmed security update guide (Website). The advisory is shared for download at msrc.microsoft.com. This vulnerability is traded as CVE-2026-45635. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $25k-$100k (estimation calculated on 06/09/2026).
Upgrading to version 10.0.17763.8880 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 10 21H2
- 10 22H2
- 10 1607
- 10 1809
- 11 23H2
- 11 24H2
- 11 25H2
- 11 26H1
- Server 2012
- Server 2012 R2
- Server 2016
- Server 2019
- Server 2022
- Server 2025
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.1VulDB Meta Temp Score: 7.1
VulDB Base Score: 8.1
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 8.1
Vendor Vector (Microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Type confusionCWE: CWE-843
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Unproven
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Upgrade: Windows 10.0.17763.8880
Timeline
06/09/2026 VulDB entry created06/09/2026 Advisory disclosed
06/09/2026 Countermeasure disclosed
06/09/2026 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-45635 (🔒)
GCVE (CVE): GCVE-0-2026-45635
GCVE (VulDB): GCVE-100-369720
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 06/09/2026 20:20Updated: 06/09/2026 20:24
Changes: 06/09/2026 20:20 (6), 06/09/2026 20:21 (32), 06/09/2026 20:24 (32)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.