CVE-2025-26521: Apache CloudStack: CKS cluster in project exposes user API keys

Published Jun 10, 2025
·
Updated

When an Apache CloudStack user-account creates a CKS-based Kubernetes cluster in a project, the API key and the secret key of the 'kubeadmin' 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 'kubeadmin' user of the CKS cluster's creator's account. An attacker who'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's account.

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 "Project Kubernetes Service Role" with the following details:

Account Name kubeadmin-<FIRSTEIGHTCHARACTERSOFPROJECTID> First Name Kubernetes Last Name Service User Account Type 0 (Normal User) Role ID <IDOFSERVICEROLE>

2. Add the Service Account to the ProjectAdd this account to the project where the Kubernetes cluster(s) are hosted. 3. Generate API and Secret KeysGenerate API Key and Secret Key for the default user of this account. 4. Update the CloudStack Secret in the Kubernetes ClusterCreate a temporary file /tmp/cloud-config with the following data:    api-url = <APIURL>     # For example: <MSURL>/client/api   api-key = <SERVICEUSERAPIKEY>   secret-key = <SERVICEUSERSECRETKEY>   project-id = <PROJECTID>

Delete the existing secret using kubectl and Kubernetes cluster config:    ./kubectl --kubeconfig kube.conf -n kube-system delete secret cloudstack-secret

Create a new secret using kubectl and Kubernetes cluster config:     ./kubectl --kubeconfig kube.conf -n kube-system create secret generic cloudstack-secret --from-file=/tmp/cloud-config

Remove the temporary file:     rm /tmp/cloud-config5. Regenerate API and Secret KeysRegenerate the API and secret keys for the original user account that was used to create the Kubernetes cluster.

Affected Software

3 affected components
Apache CloudStack<4.19.3.0, <4.20.1.0
Apache CloudStack>=4.17.0.0<4.19.3.0
Apache CloudStack>=4.20.0.0<4.20.1.0

Event History

Jun 10, 2025
CVE Published
via MITRE·11:08 PM
Data Sourced
via MITRE·11:08 PM
DescriptionWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-26521?

CVE-2025-26521 is considered a high severity vulnerability due to the risk of unauthorized access to Kubernetes clusters.

2

How do I fix CVE-2025-26521?

To fix CVE-2025-26521, upgrade Apache CloudStack to versions 4.19.3.1 or 4.20.1.1 or later.

3

What kind of projects are affected by CVE-2025-26521?

CVE-2025-26521 affects projects within Apache CloudStack that create CKS-based Kubernetes clusters.

4

Who is impacted by CVE-2025-26521?

Users with project access who can create Kubernetes clusters in Apache CloudStack are impacted by CVE-2025-26521.

5

What actions should be taken if I am using a vulnerable version of Apache CloudStack related to CVE-2025-26521?

If using a vulnerable version, it's crucial to apply the latest security updates from Apache CloudStack as soon as possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203