CVE-2026-32193: Azure Kubernetes Service Path Traversal Privilege Escalation (CVSS 8.8)

Technical summary

CVE-2026-32193 is a CWE-22 path traversal vulnerability in Azure Kubernetes Service. The flaw permits an authenticated attacker to manipulate filesystem paths in a way that bypasses directory confinement controls, enabling arbitrary code execution at a local privilege level. The CVSS 3.1 score of 8.8 (HIGH) reflects the high impact on confidentiality, integrity, and availability, combined with low attack complexity and low privilege requirements—though exploitation does require prior authenticated access to the service.

Business impact

This vulnerability affects the integrity and availability of Kubernetes clusters running on Azure. An insider or compromised user account could potentially exfiltrate sensitive data, modify workloads, or disrupt cluster operations without leaving obvious audit trails. For organizations relying on AKS for production microservices, this represents a significant insider threat and compliance risk, particularly in regulated industries where data isolation is mandatory.

Affected systems

Microsoft Azure Kubernetes Service (AKS) is affected. Organizations running containerized workloads on AKS—particularly multi-tenant clusters or those hosting sensitive applications—should identify and audit all instances. The impact scope extends to any pods or node-level processes accessible by authenticated users within the cluster.

Exploitability

Exploitation requires valid credentials or access to the AKS cluster, limiting opportunistic attacks. However, the straightforward nature of path traversal attacks and low attack complexity make this readily exploitable by any insider with basic cluster access. The vulnerability is not currently tracked in CISA's Known Exploited Vulnerabilities catalog, but public disclosure has occurred; defensive priority should be elevated accordingly.

Remediation

Apply security patches from Microsoft as they become available. Until patched, restrict AKS cluster access via Azure RBAC, implement network policies to limit pod-to-pod communication, and enforce admission controllers (such as Pod Security Standards or third-party tools) to restrict runtime capabilities. Audit and rotate credentials for all accounts with cluster access.

Patch guidance

Monitor Microsoft Azure Security Updates and the Azure Kubernetes Service release notes for patch availability. Verify patch version numbers against the official Microsoft security advisory before deployment. Test patches in non-production AKS environments first, as Kubernetes updates can affect workload scheduling and performance. Plan cluster upgrades during low-traffic windows to minimize disruption.

Detection guidance

Monitor kubelet logs and container runtime logs for unexpected filesystem access patterns, particularly any attempts to traverse parent directories (../) or access system paths from user workloads. Enable Azure Monitor for AKS and alert on suspicious authentication events or privilege escalation attempts. Implement file integrity monitoring on node filesystems to detect unauthorized modifications. Review RBAC audit logs for unusual API calls originating from service accounts with broad permissions.

Why prioritize this

Although exploitation requires prior authentication, the HIGH severity score, broad impact on confidentiality/integrity/availability, and low attack complexity warrant urgent patching. Insider threats and credential compromise are persistent risks; any vulnerability that amplifies the damage of a compromised account should be treated as priority. Organizations with multi-tenant AKS clusters face heightened risk and should prioritize this above lower-severity issues.

Risk score, explained

The CVSS 3.1 score of 8.8 reflects: local attack vector (AV:L, limiting remote attacks); low attack complexity (AC:L, straightforward exploitation); low privilege requirement (PR:L, basic user access suffices); no user interaction needed (UI:N); and scope change (S:C) with high impact across confidentiality, integrity, and availability. This puts the vulnerability firmly in HIGH severity territory, though the authentication requirement prevents a CRITICAL rating.

Frequently asked questions