Loading story…
Security researcher Justin O'Leary alleged that Azure Backup for AKS contained a critical privilege-escalation path that let a user with only the Azure Backup Contributor role gain Kubernetes cluster-admin access on a target AKS cluster. The reported issue involved Azure Trusted Access, where enabling backup could configure the backup extension with elevated permissions that could then be abused to extract secrets, deploy malicious workloads, or otherwise take over the cluster. CERT/CC reportedly validated the finding and treated it as a legitimate vulnerability.
Microsoft rejected the report, said the behavior was expected and required pre-existing administrative privileges, and did not issue a CVE or public advisory. O'Leary said the original exploit path later stopped working and that new permission checks and manual Trusted Access configuration appeared in the service, which he characterized as a silent fix; Microsoft disputed that any product changes were made. The case also highlighted disclosure-governance concerns because Microsoft, acting as a CNA for its own products, retained final authority over CVE issuance after CERT/CC closed the case under CNA hierarchy rules, leaving defenders with limited public guidance on exposure and remediation for affected AKS environments.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
After disclosure, O'Leary observed that the original attack path no longer worked and that Azure Backup for AKS appeared to add new permission checks and require manual Trusted Access configuration. The researcher characterized this as a silent fix, while Microsoft disputed that any product changes were made.
Microsoft said the reported behavior was expected and required pre-existing administrative privileges, so it did not issue a CVE or public advisory. Under CNA hierarchy rules, CERT/CC closed the case without assigning a CVE despite reportedly considering the issue valid.
Security researcher Justin O'Leary reported that users with only the Azure "Backup Contributor" role could allegedly abuse Azure Backup for AKS and Trusted Access to gain Kubernetes cluster-admin privileges on target AKS clusters.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
scworld.com
Open sourcebleepingcomputer.com
Open sourcecybernews.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Microsoft disclosed two high-severity vulnerabilities affecting hosted Azure services: **CVE-2026-32211** in **Azure MCP Server** and **CVE-2026-33105** in **Azure Kubernetes Service (AKS)**. The Azure MCP Server issue is an information disclosure flaw tied to **missing authentication for a critical function** (`CWE-306`), allowing an unauthenticated attacker to access sensitive information over the network. Its CVSS v3.1 vector, `AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`, indicates remote exploitation with no privileges or user interaction required. Microsoft also published **CVE-2026-33105**, an **improper authorization** vulnerability in AKS mapped to `CWE-285`, which could let an unauthenticated attacker **elevate privileges** remotely. The CVSS v3.1 vector, `AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`, reflects potential high impact across confidentiality, integrity, and availability. Both entries were identified as affecting **exclusively hosted services** and point defenders to Microsoft’s MSRC advisories for service-specific remediation and exposure assessment.
Jun 29, 2026
Germany's dCERT published two advisories covering **multiple vulnerabilities in Microsoft Azure**, with the later notice stating that the flaws can allow **privilege escalation**. The advisories identify Azure as the affected platform but provide no public synopsis, indicating only that several security issues were addressed across the cloud service. The paired notices suggest an evolving disclosure in which Microsoft Azure vulnerabilities were first reported broadly and then updated with a more specific impact assessment tied to elevated privileges. Organizations using Azure should review the corresponding vendor guidance and remediation information for the affected services, prioritize patching, and assess whether exposed identities, roles, or cloud resources could be affected by unauthorized privilege gains.
Jun 29, 2026
Microsoft has published multiple Security Update Guide entries for elevation-of-privilege vulnerabilities affecting cloud services including **Azure Resource Manager**, **Azure Entra ID**, **Azure AI Foundry**, and **Redis Enterprise**. The disclosed issues include `CVE-2026-47280` and `CVE-2026-24304` in Azure Resource Manager, `CVE-2026-24305` and `CVE-2025-55241` in Azure Entra ID, `CVE-2025-59271` in Redis Enterprise, and `CVE-2026-35435` in Azure AI Foundry, indicating a broader set of privilege-boundary weaknesses across Microsoft-managed platforms. Microsoft provided the most detail for **CVE-2026-35435**, describing it as a **critical** improper access control flaw in Azure AI Foundry M365 published agents that could be exploited remotely over the network without privileges or user interaction, with potential for high confidentiality impact. The company said exploitation was considered more likely, but the vulnerability had not been publicly disclosed or exploited at publication time, and the service-side issue was already fully mitigated with **no customer action required**; the remaining CVEs were listed with limited public detail in the update guide.
Jun 29, 2026