Microsoft Azure IoT Explorer communication channel to intended endpoints
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Microsoft Azure IoT Explorer. This affects an unknown function. Executing a manipulation can lead to communication channel to intended endpoints. The identification of this vulnerability is CVE-2026-23664. The attack may be launched remotely. There is no exploit available. Applying a patch is advised to resolve this issue.
Details
A vulnerability classified as problematic was found in Microsoft Azure IoT Explorer (unknown version). This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a communication channel to intended endpoints vulnerability. The CWE definition for the vulnerability is CWE-923. The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint. As an impact it is known to affect confidentiality. CVE summarizes:
Improper restriction of communication channel to intended endpoints in Azure IoT Explorer allows an unauthorized attacker to disclose information over a network.
The weakness was shared 03/10/2026 as confirmed security update guide (Website). The advisory is shared for download at msrc.microsoft.com. This vulnerability was named CVE-2026-23664. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. 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 03/13/2026).
Applying a patch is able to eliminate this problem. 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
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.5
Vendor Vector (Microsoft): 🔒
CNA Base Score: 7.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: Communication channel to intended endpointsCWE: CWE-923
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
03/10/2026 VulDB entry created03/10/2026 Advisory disclosed
03/10/2026 Countermeasure disclosed
03/13/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-23664 (🔒)
GCVE (CVE): GCVE-0-2026-23664
GCVE (VulDB): GCVE-100-349984
Entry
Created: 03/10/2026 19:03Updated: 03/13/2026 05:19
Changes: 03/10/2026 19:03 (12), 03/10/2026 19:04 (23), 03/10/2026 19:07 (33), 03/13/2026 05:19 (13)
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.