<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure on cybercrime.club</title><link>https://cybercrime.club/tags/azure/</link><description>Recent content in Azure on cybercrime.club</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Apr 2026 14:00:00 -0400</lastBuildDate><atom:link href="https://cybercrime.club/tags/azure/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-33105: Azure Kubernetes Service RBAC Bypass Scores Perfect 10.0 CVSS</title><link>https://cybercrime.club/posts/aks-cve-2026-33105-rbac-privilege-escalation/</link><pubDate>Fri, 03 Apr 2026 14:00:00 -0400</pubDate><guid>https://cybercrime.club/posts/aks-cve-2026-33105-rbac-privilege-escalation/</guid><description>&lt;p>Microsoft disclosed CVE-2026-33105 on April 3, 2026 — a critical improper authorization vulnerability in Azure Kubernetes Service that carries the maximum CVSS score of 10.0. The flaw exists in how AKS validates role-based access control (RBAC) enforcement for certain Kubernetes API requests, allowing an attacker to escalate from a standard user to full cluster administrator.&lt;/p>
&lt;p>If you run AKS clusters, stop reading and start patching.&lt;/p>
&lt;h2 id="what-happened">What Happened&lt;/h2>
&lt;p>The vulnerability is rooted in how AKS handles Kubernetes API requests related to cluster role bindings and service account permissions. Under specific conditions, the RBAC enforcement layer fails to correctly validate authorization checks, allowing an attacker to manipulate these requests and bind themselves to the &lt;code>cluster-admin&lt;/code> ClusterRole — or create new privileged service accounts — without having the permissions to do so.&lt;/p></description></item></channel></rss>