Azure LocalApplication · Microsoft

CVE-2026-42822

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-18
Fix available
A fix is available. Upgrade to 2604.2.25645 or later.
See remediation →
100/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 authentication in Azure Local Disconnected Operations allows an unauthorized attacker to elevate privileges 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 Disconnected Operations contains an improper authentication vulnerability that allows an unauthenticated remote attacker to bypass authentication mechanisms and elevate privileges to administrative levels. The flaw exists in the authentication logic for Azure Arc-enabled local infrastructure when operating in disconnected mode, enabling network-based privilege escalation without requiring valid credentials.

MitigationApply Microsoft security patches for Azure Local as they become available. Ensure network segmentation is in place and review Azure Arc authentication configurations for disconnected operations environments.

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:< 2604.2.25645
Azure Resource ManagerApplication
Affected:all versions

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
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify Azure Local deployment
    Review your Azure subscription and on-premises infrastructure to determine if Microsoft Azure Local (formerly Azure Stack HCI) is deployed in your environment. Check the Azure portal under 'Azure Arc' resources for Azure Local cluster registrations.
    Affected if Azure Local is present in the environment
  2. Check Azure Local version
    Run 'Get-AzureStackHCI' PowerShell command or check cluster properties in the Azure portal to obtain the installed version. Compare against 2604.2.25645.
    Affected if Installed version is less than 2604.2.25645
  3. Verify disconnected operations mode status
    Check Azure Arc configuration for Azure Local clusters using 'Get-AzStackHCIArcIntegration' or review cluster settings in the Azure portal to determine if disconnected operations mode is enabled.
    Affected if Disconnected operations mode is enabled on the Azure Local cluster
  4. Audit Azure Resource Manager exposure
    Review Azure Resource Manager endpoints and network configurations accessible from the Azure Local environment. Check for unauthenticated API endpoints or misconfigured authentication settings.
    Affected if Azure Resource Manager is accessible from the Azure Local environment without proper authentication controls
  5. Review administrative accounts and privilege changes
    Examine Azure Local and Azure Arc audit logs for any unexpected administrative account creation, role assignments, or privilege escalation events. Check logs for authentication attempts from unexpected sources.
    Affected if Unexpected administrative accounts or privilege escalation events are found in audit logs

The environment is affected if Azure Local version is below 2604.2.25645 with disconnected operations mode enabled, or if Azure Resource Manager is exposed without proper authentication controls.

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.

From vendor data
Upgrade available Upgrade to 2604.2.25645 or later
Fixed in 2604.2.25645
Interim mitigation

Apply Microsoft security patches for Azure Local as they become available. Ensure network segmentation is in place and review Azure Arc authentication configurations for disconnected operations environments.

Fix this in Azure Local Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42822 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42822 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