Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Network-reachable agent operation, low complexity, requires an existing low-privilege identity (PR:L), no user interaction, and a missing-auth check that crosses trust boundaries (S:C) yielding full CIA impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Missing authorization in Azure SRE Agent allows an authorized attacker to elevate privileges over a network.
AnalysisAI
Privilege elevation in Microsoft's Azure SRE Agent lets an already-authorized, low-privilege network actor gain higher privileges by exploiting a missing authorization check (CWE-862). Rated CVSS 9.9 with a scope change, the flaw means an attacker holding only limited access to the service can cross a trust boundary and reach resources or actions reserved for higher-privilege identities. No public exploit has been identified at time of analysis and it is not on the CISA KEV list, but the near-maximum score and cloud-service exposure make it a high-priority patch item.
Technical ContextAI
Azure SRE Agent is a Microsoft cloud/AI operations agent that performs site-reliability engineering tasks (incident triage, diagnostics, and automated remediation) against Azure resources, typically operating with elevated permissions over customer environments. The root cause is CWE-862 (Missing Authorization): a code path performs a sensitive operation without verifying that the calling identity is entitled to it. Because the agent brokers privileged operations on behalf of users, a missing server-side authorization check allows one authorization context to invoke actions belonging to another. The CVSS scope-change flag (S:C) indicates the vulnerable component can affect resources beyond its own security authority - consistent with a control-plane agent acting across tenant or role boundaries. No CPE strings were supplied, so exact affected component versions are not enumerable from the provided data; this is a Microsoft-hosted service, so versioning is service-side rather than a customer-installed build.
RemediationAI
Because Azure SRE Agent is a Microsoft-operated cloud service, the fix is delivered by the vendor and generally requires no customer-side package upgrade; consult the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62830 to confirm remediation status for your tenant, as no discrete customer patch version was published in the available data (Patch available per vendor advisory). As compensating controls until the service-side fix is confirmed, restrict which identities can access the SRE Agent by tightening Azure RBAC role assignments and Conditional Access so only necessary low-privilege principals retain access, review and prune the agent's own managed-identity permissions to the minimum scope (reducing blast radius of any escalation), and audit agent activity logs for anomalous privileged operations - with the trade-off that narrowing access may interrupt legitimate automated remediation workflows the agent performs.
More in Azure Sre Agent
View allSame weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-54321
GHSA-xqxc-x9r4-3vjh