dbcve.org
Azure LocalApplication · Microsoft

CVE-2026-21228

HIGH · 8.1 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 2510.0.3002 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper certificate validation in Azure Local allows an unauthorized attacker to execute code over a network.

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 confidence

Azure Local contains an improper certificate validation vulnerability that allows an unauthenticated attacker on the network to perform man-in-the-middle attacks, potentially intercepting or tampering with encrypted communications and executing arbitrary code remotely.

MitigationApply Microsoft security updates for Azure Local addressing proper certificate chain validation; verify all TLS/SSL connections validate hostnames and certificate trust chains.

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
Azure LocalApplication
Affected:< 2510.0.3002

CVSS 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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Azure Local is installed
    Check system inventory or installed Azure Local components. In Azure Local, you can verify via the Azure Stack HCI OS version displayed in Windows Admin Center or Get-AzureStackHCI cmdlet output.
    Affected if Azure Local is not present on the system - this CVE only applies to Azure Local deployments.
  2. Retrieve the Azure Local version
    Run Get-AzureStackHCI in PowerShell or check the Azure Stack HCI OS version through Windows Admin Center under the Infrastructure section.
    Affected if Unable to retrieve version information - cannot determine patch status.
  3. Compare installed version against affected range
    Compare the retrieved version number to 2510.0.3002. The version format is typically MajorBuild.Revision (e.g., 2510.0.xxxx).
    Affected if Installed version is less than 2510.0.3002 - the system is running a vulnerable version without the certificate validation fix.
  4. Verify network connectivity exposure
    Check if the Azure Local system accepts TLS/SSL connections from external networks or participates in cluster communication over untrusted networks.
    Affected if System has external network exposure and is running a version below 2510.0.3002 - the improper certificate validation could be exploited in transit.

A system is affected if it runs Microsoft Azure Local with a version number lower than 2510.0.3002 and has network connectivity where TLS/SSL traffic could be intercepted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2510.0.3002 or later
Fixed in 2510.0.3002
Interim mitigation

Apply Microsoft security updates for Azure Local addressing proper certificate chain validation; verify all TLS/SSL connections validate hostnames and certificate trust chains.

Recommended fix Moderate confidence

Azure Local version 2510.0.3002 or later

  1. 1. Back up all critical data and configurations on the Azure Local system before initiating any upgrade.
  2. 2. Review the Azure Local update documentation at docs.microsoft.com/azure/local for upgrade prerequisites and procedures.
  3. 3. Ensure the system meets all prerequisites for version 2510.0.3002 including compatibility requirements.
  4. 4. Apply the update to Azure Local to version 2510.0.3002 or later using the Azure Local admin center or appropriate update mechanism.
  5. 5. Verify the update was successful by checking the Azure Local version in the admin center.
  6. 6. Confirm that affected services are running normally after the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Azure Local Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21228 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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