What is the CVSS score of CVE-2025-26628?

CVE-2025-26628 has a CVSS 3.1 base score of 7.3 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. EPSS exploitation probability: 0.6%.

Which versions of Azure Local Cluster are affected by CVE-2025-26628?

Organizations using Insufficiently protected credentials in Azure Local Cluster face moderate risk from CVE-2025-26628 rated CVSS 7.3.

How to fix or mitigate CVE-2025-26628?

Within 7 days: Identify all affected systems and apply vendor patches promptly. Monitor vendor channels for patch availability.

Azure Local Cluster CVE-2025-26628

HIGH

Insufficiently Protected Credentials (CWE-522)

2025-04-08 secure@microsoft.com

Microsoft Information Disclosure Azure Local Cluster

7.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.3 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

Low

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:35 vuln.today

CVE Published

Apr 08, 2025 - 18:15 nvd

HIGH 7.3

DescriptionCVE.org

Insufficiently protected credentials in Azure Local Cluster allows an authorized attacker to disclose information locally.

AnalysisAI

Insufficiently protected credentials in Azure Local Cluster allows an authorized attacker to disclose information locally. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Insufficiently Protected Credentials (CWE-522), which allows attackers to obtain user credentials due to weak protection mechanisms. Insufficiently protected credentials in Azure Local Cluster allows an authorized attacker to disclose information locally. Affected products include: Microsoft Azure Local Cluster.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Hash passwords with strong algorithms (bcrypt, argon2), encrypt credentials in transit and at rest, never log credentials.