Microsoft Azure IoT Explorer binding to an unrestricted ip address
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft Azure IoT Explorer and classified as problematic. Affected is an unknown function. The manipulation results in binding to an unrestricted ip address. This vulnerability is known as CVE-2026-21528. It is possible to launch the attack remotely. No exploit is available. It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Microsoft Azure IoT Explorer (the affected version is unknown). It has been classified as problematic. Affected is an unknown code. The manipulation with an unknown input leads to a binding to an unrestricted ip address vulnerability. CWE is classifying the issue as CWE-1327. The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely. This is going to have an impact on confidentiality. CVE summarizes:
Binding to an unrestricted ip address in Azure IoT Explorer allows an unauthorized attacker to disclose information over a network.
The weakness was published 02/10/2026 as confirmed security update guide (Website). The advisory is shared for download at msrc.microsoft.com. This vulnerability is traded as CVE-2026-21528. The exploitability is told to be easy. 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 $0-$5k (estimation calculated on 02/19/2026).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 6.5
Vendor Vector (Microsoft): 🔒
CNA Base Score: 6.5
CNA 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: Binding to an unrestricted ip addressCWE: CWE-1327 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Unproven
EPSS Score: 🔒
EPSS Percentile: 🔒
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: PatchStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline
02/10/2026 VulDB entry created02/10/2026 Advisory disclosed
02/10/2026 Countermeasure disclosed
02/19/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-21528 (🔒)
GCVE (CVE): GCVE-0-2026-21528
GCVE (VulDB): GCVE-100-345300
Entry
Created: 02/10/2026 19:35Updated: 02/19/2026 20:14
Changes: 02/10/2026 19:35 (2), 02/10/2026 19:36 (33), 02/10/2026 19:39 (33), 02/11/2026 18:02 (12), 02/19/2026 20:14 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.