CVE-2025-59292: Azure Compute Gallery Privilege Escalation

CVE-2025-59292 Overview

CVE-2025-59292 is a local privilege escalation vulnerability affecting Confidential Azure Container Instances within Microsoft Azure Compute Gallery. The flaw stems from external control of a file name or path [CWE-73], allowing an authorized attacker with high privileges to escalate their access on the affected system. Microsoft published the advisory on October 14, 2025.

The issue affects containerized workloads that rely on confidential compute isolation guarantees. An attacker who successfully exploits the vulnerability can compromise confidentiality, integrity, and availability across trust boundaries because of the scope change indicated in the CVSS vector.

Critical Impact
Successful exploitation grants an authorized local attacker elevated privileges and crosses the security scope of the container isolation model, impacting resources beyond the compromised component.

Affected Products

Microsoft Azure Compute Gallery
Confidential Azure Container Instances
Azure workloads dependent on the affected image distribution component

Discovery Timeline

2025-10-14 - CVE CVE-2025-59292 published to NVD
2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-59292

Vulnerability Analysis

The vulnerability is classified under CWE-73: External Control of File Name or Path. The affected component accepts file paths or names from an external source without sufficient validation. An authorized attacker with high privileges can supply crafted path input that redirects file operations to attacker-chosen locations.

Because the target is Confidential Azure Container Instances, this class of flaw undermines the isolation and integrity guarantees that customers rely on for sensitive workloads. The scope change in the CVSS metric confirms that the impact extends beyond the vulnerable component to other resources managed by Azure.

Root Cause

The root cause is improper validation and sanitization of externally supplied file identifiers used by the Confidential Azure Container Instances component. When user-controlled input reaches file system operations without canonicalization or restriction to an allowed directory, the process can read, write, or execute files outside the intended boundary. This is the classic pattern behind [CWE-73].

Attack Vector

The attack requires local access with high privileges and no user interaction. An authorized principal within the Azure environment submits crafted path input to the vulnerable interface. The service acts on that input under its own privileges, giving the attacker access to resources they were not authorized to reach.

No public proof-of-concept exists, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Refer to the Microsoft Security Update Guide for CVE-2025-59292 for authoritative technical details.

Detection Methods for CVE-2025-59292

Indicators of Compromise

Unexpected file access patterns in Confidential Azure Container Instances logs, particularly paths containing ../ traversal sequences or absolute paths outside the container's expected working directories.
Azure Activity Log entries showing unusual operations against Compute Gallery image resources initiated by service principals or managed identities that do not normally touch those resources.
Container workload processes accessing files outside their mount namespace or attempting to reference host paths.

Detection Strategies

Correlate Azure Resource Manager audit logs with container runtime telemetry to identify privileged operations that reference externally supplied path parameters.
Alert on any successful file operations by the confidential container control plane that resolve to paths outside the expected image staging directories.
Baseline normal path arguments used by Compute Gallery operations and flag deviations, especially those originating from high-privilege identities.

Monitoring Recommendations

Enable diagnostic settings on Azure Compute Gallery and Container Instances resources and forward logs to a centralized analytics platform.
Monitor Entra ID sign-ins and role assignments for the identities with permission to interact with Confidential Azure Container Instances.
Track privilege escalation indicators such as new role assignments, unexpected Microsoft.ContainerInstance API calls, and modifications to gallery image definitions.

How to Mitigate CVE-2025-59292

Immediate Actions Required

Review the Microsoft Security Update Guide for CVE-2025-59292 and apply the mitigations Microsoft has published for affected Azure services.
Audit role assignments on Azure Compute Gallery and Confidential Azure Container Instances and remove any principals that do not require high-privilege access.
Rotate credentials and access keys for service principals and managed identities that interact with the affected components.

Patch Information

Microsoft addressed this vulnerability through service-side updates to Azure. Because Azure Compute Gallery and Confidential Azure Container Instances are managed services, no customer-installed patch is required. Confirm remediation status by consulting the Microsoft Security Response Center advisory linked above.

Workarounds

Enforce least privilege for all identities that can create, modify, or deploy Confidential Container Instances or gallery images.
Restrict access to Azure Compute Gallery resources using Azure role-based access control and Conditional Access policies that require strong authentication.
Isolate sensitive confidential workloads into dedicated subscriptions with tighter policy guardrails until service-side remediation is verified.

bash

# Example: audit role assignments on an Azure Compute Gallery resource
az role assignment list \
  --scope "/subscriptions/<SUB_ID>/resourceGroups/<RG>/providers/Microsoft.Compute/galleries/<GALLERY_NAME>" \
  --output table

# Remove an unnecessary high-privilege assignment
az role assignment delete \
  --assignee <PRINCIPAL_ID> \
  --role "Contributor" \
  --scope "/subscriptions/<SUB_ID>/resourceGroups/<RG>/providers/Microsoft.Compute/galleries/<GALLERY_NAME>"