Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege Azure Arc access
-
DeliveryAbuse confused-deputy flaw (CWE-441)
-
ExploitCoerce Arc control plane to act as proxy
-
ExecutionCross trust boundary (scope change)
-
ImpactGain elevated control of connected resources
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service Proxy/intermediary controls
|
| Exploitation Conditions | Exploitation requires low-privilege authenticated access to an Azure Arc context (PR:L in the vendor vector), performed remotely over the network with no user interaction (AV:N/UI:N). The specific Arc feature, API, or configuration that triggers the confused-deputy condition (CWE-441) is not described in the available sources, so the exact prerequisite setting cannot be named from the provided data. Limiting factors: an attacker must already possess some valid low-level Arc/Azure identity (it is not fully unauthenticated), and the scope change (S:C) implies the impact crosses the Arc management trust boundary into connected resources rather than staying local. No non-default configuration is documented as required, but absence of detail means this cannot be confirmed. |
| Impact | Signals conflict sharply and must be weighed, not averaged. Microsoft's CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, base 9.9) describes a network-reachable, low-complexity flaw needing only low privileges, no user interaction, with a scope change and total confidentiality/integrity/availability impact - consistent with the 'Technical Impact: total' and 'Automatable: yes' entries in the SSVC record. The vuln.today decision label is 'act_now,' which aligns with that high severity and automatability. However, the real-world exploitation signals are much softer: SSVC 'Exploitation: none,' no CISA KEV listing, and no PoC or exploit reference in the provided sources, so this is NOT confirmed as actively exploited. EPSS is only 0.49% (41st percentile), i.e. low predicted 30-day exploitation probability, which contrasts with the 9.9 base score and 'act_now' label - a classic 'high-severity, not-yet-exploited' profile. The practical reading: this is a high-priority patch candidate because impact is total, the flaw is automatable, and privileges required are low, but there is currently no evidence of exploitation in the wild, so the urgency derives from potential blast radius (scope change across the Azure Arc hybrid-management trust boundary) rather than observed attacks. The description is a single stock title with no mechanism detail, so the exact trigger is not described in the available sources and the CVSS metrics should be treated as vendor-asserted, not independently reproducible. |
| Exploit ScenarioDerived | An attacker holding only low-privilege authenticated access within an Azure Arc-managed environment abuses a confused-deputy condition (CWE-441) to have the Arc control plane act on its behalf across a trust boundary, gaining elevated control over connected resources. Because the CVSS vector is AV:N/AC:L/PR:L/UI:N with a scope change, the action is remote, low-complexity, needs no victim interaction, and reaches resources beyond the attacker's original authorization. No public exploit has been identified at time of analysis, and the exact trigger is not described in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Oct 31, 2026
Azure Arc's confused-deputy flaw (CWE-441) allows a low-privileged, authenticated remote actor to cross the service's management trust boundary and achieve high confidentiality, integrity, and availability impact across connected resources, producing a 9.9 CVSS score with Scope:Changed. Microsoft Azure Arc is affected broadly (CPE cpe:2.3:a:microsoft:azure_arc:-), and exploitation requires a valid low-level Arc/Azure identity rather than being fully unauthenticated. No public exploit has been identified at time of analysis and no CISA KEV entry is present in the provided data, with EPSS low at 0.49% (41st percentile); the vuln.today decision label is act_now because CISA SSVC rates technical impact as total and automation as feasible.
Earlier versions of this analysis (2)
Elevation of privilege in Microsoft Azure Arc, the hybrid and multicloud control plane that projects on-premises and non-Azure servers, Kubernetes clusters and data services into Azure Resource Manager, is rated by NVD at CVSS 3.1 base 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), implying remote, low-complexity, unauthenticated attackers could reach high confidentiality, integrity and availability impact against Arc-enrolled environments. Exposure is limited to organizations that have actually onboarded resources to Arc, and the PR:N rating conflicts both with the Elevation-of-Privilege classification (which normally presumes a prior foothold) and with our internal assessment of AV:N/AC:L/PR:L/UI:N/S:C, so the unauthenticated assumption should be verified against the Microsoft update guide before it is used for risk decisions. There is no confirmed active exploitation (CVE is not in CISA KEV), no public exploit code identified at time of analysis, EPSS is low at 0.49% (41st percentile), and CISA SSVC records Exploitation: none alongside Automatable: yes and Technical Impact: total.
Elevation of privilege in Microsoft Azure Arc allows a network-reachable attacker to abuse the service as a privileged intermediary and affect resources outside the vulnerable component itself, producing full confidentiality, integrity, and availability impact across the scoped environment. The published CVSS 3.1 vector scores this 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), reflecting low attack complexity, a scope change, and complete impact to the impacted resources; our independent assessment rates the same flaw with the privilege prerequisite raised to low (PR:L) and notes that the PR:N claim conflicts with typical elevation-of-privilege semantics and should be confirmed with MSRC before treating exploitation as fully unauthenticated. Only Azure Arc deployments are affected - hybrid or multicloud servers onboarded through the connected machine agent, Arc-enabled Kubernetes clusters, and Arc-enabled data services - and no public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
No exact fixed version is listed in the provided data; Microsoft's MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69399) is the authoritative source for the patched Azure Arc build, and organizations should apply that vendor update as the complete fix. Because exploitation requires only a low-privileged Arc/Azure identity, reduce exposure in the interim by tightly restricting who can hold Arc onboarding and role-assignment permissions, reviewing existing low-privilege Arc roles for unnecessary cross-resource authority, and monitoring for unexpected scope-crossing operations; these controls lower the attack surface but do not remove the confused-deputy flaw. No specific product workaround is documented in the available sources, and the act_now priority reflects the total technical impact rather than confirmed exploitation.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-441 (Confused Deputy) is the root-cause class: the Azure Arc control plane can act on behalf of a caller and, in this case, does not adequately bind the caller's low privilege to the authority it exercises over connected resources. The CVSS:3.1 vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H confirms remote, low-complexity exploitation by an authenticated low-privileged user with no user interaction, and the S:C component means the security authority changes from the Arc management context to the managed-resource context. The CPE cpe:2.3:a:microsoft:azure_arc:-:*:*:*:*:*:*:* identifies Azure Arc as the affected product but does not encode a version, and EUVD lists the affected version only as 'Azure ARC -'. The specific Arc feature, API, or configuration that triggers the confused-deputy condition is not described in the available sources.
Know when Azure Arc gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Keeps vendor metrics: remote and low-complexity with low-privilege auth (PR:L, not PR:N, since some Arc identity is needed), scope change across the Arc trust boundary, total CIA impact; description too sparse to lower any metric.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionNVD
Azure Arc Elevation of Privilege Vulnerability
Executive ViewAI
A critical confused-deputy vulnerability in Microsoft Azure Arc allows a low-privileged, authenticated user to break the service's management trust boundary and compromise the confidentiality, integrity, and availability of connected resources across the estate. Because Azure Arc is Microsoft's control plane for managing on-premises, multicloud, and edge servers alongside native Azure resources, a successful exploitation could cascade into unauthorized control over a broad set of managed infrastructure - making this a potential enterprise-wide integrity and availability concern for any organization using Arc to govern hybrid or multicloud assets. Leadership should care because the blast radius extends beyond a single system to the management layer itself, and no vendor patch is currently available.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce least privilege and credential rotation for all Arc/Azure identities; restrict network access to Arc-connected machines and agents to trusted sources; apply conditional access, MFA, and just-in-time elevation; segment Arc-managed resources to limit cross-boundary blast radius; enable centralized logging and monitoring of Arc and Azure Activity logs with alerting on anomalous cross-resource operations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Privilege escalation in Microsoft Azure Arc allows an unauthorized, network-based attacker to bypass authorization check
Path traversal (CWE-22) in Microsoft Azure Arc, rated CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), could allow a remo
Azure Guest Configuration and Azure Arc-enabled servers Elevation of Privilege Vulnerability. Rated high severity (CVSS
EUVD-2026-82586
GHSA-h8pp-hmv6-8cpq
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB