https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 01:12:25 +0000 https://cve.radiocsirt.org/vuln/cve-2025-26521 <p><strong>Affected:</strong> Apache Software Foundation Apache CloudStack</p> <p>When an Apache CloudStack user-account creates a CKS-based Kubernetes cluster in a project, the API key and the secret key of the &#39;kubeadmin&#39; user of the caller account are used to create the secret config in the CKS-based Kubernetes cluster. A member of the project who can access the CKS-based Kubernetes cluster, can also access the API key and secret key of the &#39;kubeadmin&#39; user of the CKS cluster&#39;s creator&#39;s account. An attacker who&#39;s a member of the project can exploit this to impersonate and perform privileged actions that can result in complete compromise of the confidentiality, integrity, and availability of resources owned by the creator&#39;s account.</p> <p>CKS users are recommended to upgrade to version 4.19.3.0 or 4.20.1.0, which fixes this issue.Updating Existing Kubernetes Clusters in ProjectsA service account should be created for each project to provide limited access specifically for Kubernetes cluster providers and autoscaling. Follow the steps below to create a new service account, update the secret inside the cluster, and regenerate existing API and service keys:1. Create a New Service AccountCreate a new account using the role &#34;Project Kubernetes Service Role&#34; with the following details:</p> <p>Account Name kubeadmin-&lt;FIRST_EIGHT_CHARACTERS_OF_PROJECT_ID&gt; First Name Kubernetes Last Name Service User Account Type 0 (Normal User) Role ID &lt;ID_OF_SERVICE_ROLE&gt;</p> <p>2. Add the Service Account to the ProjectAdd this account to the project where the Kubernetes cluster(s) are host…</p> <p><strong>Affected:</strong> Apache Software Foundation Apache CloudStack</p> <p>When an Apache CloudStack user-account creates a CKS-based Kubernetes cluster in a project, the API key and the secret key of the &#39;kubeadmin&#39; user of the caller account are used to create the secret config in the CKS-based Kubernetes cluster. A member of the project who can access the CKS-based Kubernetes cluster, can also access the API key and secret key of the &#39;kubeadmin&#39; user of the CKS cluster&#39;s creator&#39;s account. An attacker who&#39;s a member of the project can exploit this to impersonate and perform privileged actions that can result in complete compromise of the confidentiality, integrity, and availability of resources owned by the creator&#39;s account.</p> <p>CKS users are recommended to upgrade to version 4.19.3.0 or 4.20.1.0, which fixes this issue.Updating Existing Kubernetes Clusters in ProjectsA service account should be created for each project to provide limited access specifically for Kubernetes cluster providers and autoscaling. Follow the steps below to create a new service account, update the secret inside the cluster, and regenerate existing API and service keys:1. Create a New Service AccountCreate a new account using the role &#34;Project Kubernetes Service Role&#34; with the following details:</p> <p>Account Name kubeadmin-&lt;FIRST_EIGHT_CHARACTERS_OF_PROJECT_ID&gt; First Name Kubernetes Last Name Service User Account Type 0 (Normal User) Role ID &lt;ID_OF_SERVICE_ROLE&gt;</p> <p>2. Add the Service Account to the ProjectAdd this account to the project where the Kubernetes cluster(s) are host…</p> https://cve.radiocsirt.org/vuln/cve-2025-26521