dbcve.org
Azure Kubernetes ServiceApplication · Microsoft

CVE-2026-32193

HIGH · 8.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 2026-02-13.5 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper limitation of a pathname to a restricted directory ('path traversal') in Microsoft Azure Kubernetes Service allows an authorized attacker to execute code locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Path traversal vulnerability in Microsoft Azure Kubernetes Service (AKS) allows an authorized attacker to escape restricted directories and execute code locally on affected AKS nodes or infrastructure components.

MitigationApply Microsoft-provided patches by upgrading to fixed AKS versions; review and limit unnecessary permissions for authorized users to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure Kubernetes ServiceApplication
Affected:< 2026-02-13.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check AKS cluster control plane version
    Run `az aks show -g <resource-group> -n <cluster-name> --query "kubernetesVersion"` or use Azure Portal to view the AKS cluster properties. Compare the version to 2026-02-13.5.
    Affected if The AKS cluster version is earlier than 2026-02-13.5 (the version number will be lower, for example 2026-01-15.3 or any version prior to the patch release).
  2. Verify AKS cluster provisioning state
    Run `az aks show -g <resource-group> -n <cluster-name> --query "provisioningState"` to confirm the cluster is in a Running state.
    Affected if The cluster exists and is Running, meaning the vulnerable AKS service component is actively handling requests.
  3. Check for authenticated user access to AKS management APIs
    Review Azure RBAC role assignments on the AKS resource using `az role assignment list --scope /subscriptions/<sub-id>/resourceGroups/<rg>/providers/Microsoft.ContainerService/managedClusters/<cluster>` or Azure Portal IAM blade.
    Affected if Any Azure AD authenticated principal (user, service principal, or managed identity) has at least Reader or higher permissions to the AKS resource, as the vulnerability requires an authenticated attacker.
  4. Inspect AKS cluster networking configuration
    Run `az aks show -g <resource-group> -n <cluster-name> --query "networkProfile"` to check if the API server is exposed via public or private endpoints.
    Affected if The AKS API server has a public endpoint (enablePublicNetworkAccess: true) or private endpoint configuration that permits authenticated access from outside the cluster.

You are affected if your AKS cluster version is earlier than 2026-02-13.5 AND at least one authenticated Azure AD principal has access to manage or interact with the AKS resource.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026-02-13.5 or later
Fixed in 2026-02-13.5
Interim mitigation

Apply Microsoft-provided patches by upgrading to fixed AKS versions; review and limit unnecessary permissions for authorized users to reduce attack surface.

Recommended fix High confidence

2026-02-13.5 (or later)

  1. Identify the current Kubernetes version of your AKS cluster: `az aks show -g <resource-group-name> -n <cluster-name> --query kubernetesVersion`.
  2. Check available AKS versions for your region: `az aks get-versions -l <location> --output table`.
  3. Upgrade the AKS cluster to version 2026-02-13.5 (or a later version) using: `az aks upgrade --resource-group <resource-group-name> --name <cluster-name> --kubernetes-version 2026-02-13.5`.
  4. Verify the upgrade succeeded by running `az aks show -g <resource-group-name> -n <cluster-name> --query kubernetesVersion` and confirming the version is 2026-02-13.5 or later.
  5. Validate that all workloads and node pools are running correctly and review the AKS release notes for any known issues or required post‑upgrade actions.
Caveat Review the AKS release notes for version 2026-02-13.5 for any breaking changes; test workloads in a staging environment before upgrading production.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Azure Kubernetes Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32193 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data