dbcve.org
Azure Kubernetes ServiceApplication · Microsoft

CVE-2026-33105

CRITICAL · 9.8 CVSS v3.1 Developing Published 2026-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 authorization in Microsoft Azure Kubernetes Service allows an unauthorized attacker to elevate privileges over a network.

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 · low confidence

This is an authorization bypass vulnerability in Microsoft Azure Kubernetes Service (AKS) that allows an unauthenticated attacker to elevate their privileges within the cluster over a network. The flaw permits unauthorized access to higher-privilege operations, potentially granting access to sensitive workloads or administrative functions.

MitigationMonitor Microsoft Security Response Center for the official patch and apply AKS updates promptly. Implement network segmentation and least-privilege RBAC policies as defense-in-depth measures until the patch is applied.

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:all versions

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify AKS clusters in your subscription
    Run 'az aks list --output table' to list all Azure Kubernetes Service clusters in your subscription, or use Azure Portal to view AKS resources
    Affected if Any AKS cluster exists in the subscription - all versions are affected per the CVE description
  2. Check API server network exposure
    Run 'az aks show -g <resource-group> -n <cluster-name> --query apiServerAccessProfile' to review whether the AKS API server is exposed to the internet or has restricted authorized IP ranges configured
    Affected if API server is publicly accessible without IP restrictions, as the CVE allows network-based unauthenticated exploitation
  3. Review RBAC role bindings
    Run 'kubectl get rolebindings --all-namespaces' and 'kubectl get clusterrolebindings' to examine current role assignments. Look for unexpected bindings to elevated roles such as cluster-admin or admin
    Affected if Role bindings grant excessive privileges to unauthenticated or low-privilege principals, enabling the privilege escalation described in the CVE
  4. Audit cluster activity logs
    In Azure Portal, navigate to the AKS cluster resource and review Activity Log for events around 'create role' 'create rolebinding' or 'escalate' operations, or query via 'az monitor activity-log list --resource-group <rg>'
    Affected if Logs show unauthorized role modifications or privilege escalation events that may indicate exploitation attempts
  5. Check for anonymous access to API server
    Run 'kubectl auth can-i --list --as=system:anonymous' to determine if anonymous authentication is enabled on the cluster API server
    Affected if Anonymous access is enabled, as unauthenticated exploitation is a key component of this vulnerability

If you have any AKS cluster running and it is network-accessible with potentially misconfigured RBAC or anonymous access enabled, your environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Monitor Microsoft Security Response Center for the official patch and apply AKS updates promptly. Implement network segmentation and least-privilege RBAC policies as defense-in-depth measures until the patch is applied.

Fix this in Azure Kubernetes Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33105 — 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-33105 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