CVE-2025-26628
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficiently protected credentials in Azure Local Cluster allows an authorized attacker to disclose information locally.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsufficiently protected credentials in Azure Local Cluster allows an authorized attacker to locally access and disclose sensitive information. The vulnerability stems from improper storage or protection of credentials within the local cluster environment, enabling a user with local access to extract credentials that should be secured.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2411.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Azure Local Cluster versionRun the command to retrieve the installed version of Azure Local Cluster (e.g., via Azure Stack HCI diagnostics or cluster management tools). Compare the version number to the affected range: versions prior to 2411.2 are vulnerable.Affected if The installed version is lower than 2411.2
-
Locate credential storage locationsInspect the local cluster environment for directories or configuration files where credentials may be stored, such as cluster configuration stores, local user directories, or credential configuration files.Affected if Credentials are stored locally on the cluster nodes without additional protection
-
Examine stored credentials for encryptionOpen or inspect the identified credential storage locations and determine whether the stored credentials are encrypted, hashed, or stored in plaintext format.Affected if Credentials are found in plaintext or use weak/obvious encoding without proper encryption at rest
-
Verify credential protection mechanismsCheck if the cluster is configured to use external secure credential storage solutions (such as Azure Key Vault integration) or has encryption at rest enabled for local credential storage.Affected if No encryption at rest or external secure credential storage is configured, and credentials reside in unprotected local storage
-
Assess access controls on credential storageReview file system permissions and access controls on directories or files containing credentials to determine if local users other than intended administrators can read them.Affected if Local non-privileged users have read access to credential storage files or directories
A user is affected if their Azure Local Cluster version is below 2411.2 AND credentials are stored locally without encryption or proper access controls, allowing local users to read sensitive credential data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2411.2
Implement proper credential protection mechanisms such as encryption at rest, secure credential storage solutions (e.g., Azure Key Vault integration), and ensure credentials are not stored in plaintext. Follow least-privilege access controls to limit exposure.
2411.2 or later
- Identify current Azure Local Cluster version to confirm it is below 2411.2
- Review upgrade documentation and plan a maintenance window
- Back up current cluster configuration and credentials
- Upgrade Azure Local Cluster to version 2411.2 or later
- Verify the upgrade was successful and credentials are now properly protected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26628 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data