Microsoft Azure Local Cluster insufficiently protected credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Microsoft Azure Local Cluster. The affected element is an unknown function. This manipulation causes insufficiently protected credentials. This vulnerability is registered as CVE-2025-26628. The attack needs to be launched locally. No exploit is available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in Microsoft Azure Local Cluster (version now known) and classified as problematic. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. The CWE definition for the vulnerability is CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. As an impact it is known to affect confidentiality. The summary by CVE is:
Insufficiently protected credentials in Azure Local Cluster allows an authorized attacker to disclose information locally.
The weakness was published 04/08/2025 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. This vulnerability is known as CVE-2025-26628. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 5.9VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.3
VulDB Temp Score: 2.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.3
Vendor Vector (Microsoft): 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 7.3
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: Insufficiently protected credentialsCWE: CWE-522
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
04/08/2025 🔍04/08/2025 🔍
04/08/2025 🔍
01/16/2026 🔍
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-26628 (🔍)
GCVE (CVE): GCVE-0-2025-26628
GCVE (VulDB): GCVE-100-303925
Entry
Created: 04/08/2025 19:37Updated: 01/16/2026 16:14
Changes: 04/08/2025 19:37 (1), 04/08/2025 19:38 (31), 04/08/2025 19:41 (36), 01/16/2026 16:14 (22)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.