dbcve.org
Azure ArcApplication · Microsoft

CVE-2026-24302

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 access control in Azure Arc 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

Improper access control in Azure Arc enables an unauthorized attacker to elevate privileges over a network. The vulnerability involves a flaw in access control mechanisms that allows privilege escalation, which combined with network accessibility and critical severity (CVSS 9.8) indicates the flaw can be exploited remotely without authentication.

MitigationApply available patches or mitigations for Azure Arc; ensure network segmentation and follow least-privilege principles for Azure Arc service accounts and role assignments until a specific fix is confirmed.

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 ArcApplication
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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 Arc deployment exists
    Use Azure CLI command 'az connectedmachine list' or 'az arcdata list' to enumerate Azure Arc resources in your subscription. Alternatively, check Azure Portal for Azure Arc-enabled servers, Kubernetes clusters, or data services.
    Affected if Any Azure Arc resources (servers, Kubernetes clusters, or data services) are found in the subscription.
  2. Verify network accessibility of Azure Arc services
    Check if Azure Arc agents or services are listening on accessible network interfaces. For Azure Arc-enabled servers, verify port 443/HTTPS connectivity to Azure endpoints is open and accessible from untrusted networks.
    Affected if Azure Arc endpoints are reachable from network segments outside the trusted administrative zone.
  3. Review Azure Arc service principal role assignments
    Run 'az role assignment list --assignee <service-principal-id>' for Azure Arc-related service principals or managed identities. Check for overly permissive roles such as Owner, Contributor, or User Access Administrator assigned to Azure Arc identities.
    Affected if Azure Arc service accounts or managed identities have high-privilege role assignments (Owner, Contributor, or excessive permissions) that enable privilege escalation.
  4. Check Azure Arc agent configuration and status
    On Azure Arc-enabled servers, inspect the connected machine agent (hybrid_agent) status using 'az connectedmachine show -n <machine-name> -g <resource-group>'. Verify agent version and connectivity state.
    Affected if Azure Arc agent is connected and running, indicating the vulnerable access control mechanism is active.
  5. Audit Azure Arc resource provider registrations
    Use 'az provider show --namespace Microsoft.HybridCompute' and 'az provider show --namespace Microsoft.AzureArcData' to verify Azure Arc resource providers are registered, confirming Arc services are in use.
    Affected if Azure Arc resource providers (Microsoft.HybridCompute, Microsoft.AzureArcData) are registered in the subscription.

If Azure Arc resources are deployed and network-accessible, the environment is affected by this vulnerability since all versions contain the improper access control flaw.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available patches or mitigations for Azure Arc; ensure network segmentation and follow least-privilege principles for Azure Arc service accounts and role assignments until a specific fix is confirmed.

Fix this in Azure Arc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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