Full Report
A security researcher claims Microsoft quietly fixed an Azure Backup for AKS vulnerability after rejecting his report, and without issuing a CVE. Microsoft disputes the claim, telling BleepingComputer the behavior was expected and that "no product changes were made," despite the researcher documenting a silent fix. [...]
Analysis Summary
# Vulnerability: Azure Backup for AKS Privilege Escalation (Silent Patch)
## CVE Details
- **CVE ID:** No CVE issued (Microsoft rejected the report; tracked by CERT/CC as VU#284781)
- **CVSS Score:** N/A (Researcher estimates Critical)
- **CWE:** CWE-441: Confused Deputy
## Affected Systems
- **Products:** Azure Backup for AKS (Azure Kubernetes Service)
- **Versions:** All versions prior to May 2026
- **Configurations:** Environments utilizing the "Backup Contributor" Azure RBAC role and the "Trusted Access" feature for AKS.
## Vulnerability Description
The vulnerability resided in how the Azure Backup service interacted with AKS via "Trusted Access." The researcher discovered that a user assigned the low-privileged **Backup Contributor** role could enable backup on a target cluster without possessing any existing Kubernetes-native permissions.
When backup was enabled, the Azure platform automatically configured the Trusted Access relationship, granting the backup extension **cluster-admin** privileges. By exploiting this automated trust setup, a Backup Contributor could perform unauthorized actions, such as extracting secrets or deploying malicious workloads, effectively escalating their privileges to full cluster administrator.
## Exploitation
- **Status:** PoC documented by researcher; reported functionality silenced by vendor updates as of May 2026.
- **Complexity:** Low
- **Attack Vector:** Network (Cloud API/Azure Portal)
## Impact
- **Confidentiality:** High (Full access to Kubernetes secrets and data)
- **Integrity:** High (Ability to deploy or modify workloads)
- **Availability:** High (Ability to delete or disrupt cluster resources)
## Remediation
### Patches
Microsoft officially states "no product changes were made," however, researchers observed a **silent fix** in May 2026. The platform now appears to:
1. Require manual configuration of Trusted Access before backups can be enabled.
2. Enforce additional permission checks (Reader permissions on the AKS cluster and snapshot Resource Group).
### Workarounds
- **Principle of Least Privilege:** Audit all users with the "Backup Contributor" role and restrict this role only to highly trusted identities.
- **Manual Configuration:** Ensure "Trusted Access" is explicitly managed and monitored rather than relying on automated service setups.
## Detection
- **Indicators of Compromise:**
- Unusually high volumes of backup/restore activity from unexpected accounts.
- Unexpected "Trusted Access" role bindings appearing in AKS clusters.
- **Detection methods:**
- Monitor Azure Activity Logs for the `Microsoft.KubernetesConfiguration/extensions/write` operation.
- Monitor Kubernetes Audit Logs for actions performed by the `system:serviceaccount:azure-backup` identity that do not align with scheduled backup windows.
## References
- hxxp[://]olearysec[.]com/research/azure-backup-aks-silent-patch/
- hxxps[://]www[.]bleepingcomputer[.]com/news/security/microsoft-rejects-critical-azure-vulnerability-report-no-cve-issued/
- hxxps[://]learn[.]microsoft[.]com/en-us/azure/backup/azure-kubernetes-service-cluster-manage-backups