{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-26521 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-26521 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-26521 is a high-severity vulnerability in Apache Cloudstack, published on 10 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-26521 and fix it if it is affected.\n\nWhat it is: CVE-2025-26521 is a high-severity vulnerability in Apache Cloudstack, published on 10 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-26521 in the wild and no public exploit code.\n\nAffected product: Apache Cloudstack. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-26521/ (Markdown: https://insights.sbomify.com/CVE-2025-26521/index.md)","id":"CVE-2025-26521","markdown":"https://insights.sbomify.com/CVE-2025-26521/index.md","name":"CVE-2025-26521","record":{"aliases":["GHSA-r5jq-h47c-74h3"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache CloudStack","requires_auth":"low_privilege","summary":"Project members can access the creator's API keys from Kubernetes cluster secrets, allowing account impersonation and resource compromise.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"cloudstack","vendor":"apache"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.\n\nCKS 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:\n\nAccount Name\nkubeadmin-\u003cFIRST_EIGHT_CHARACTERS_OF_PROJECT_ID\u003e\nFirst Name\nKubernetes\nLast Name\nService User\nAccount Type\n0 (Normal User)\nRole ID\n\u003cID_OF_SERVICE_ROLE\u003e\n\n2. Add the Service Account to the ProjectAdd this account to the project where the Kubernetes cluster(s) are hosted.\n3. Generate API and Secret KeysGenerate API Key and Secret Key for the default user of this account.\n4. Update the CloudStack Secret in the Kubernetes ClusterCreate a temporary file `/tmp/cloud-config` with the following data:\n   api-url = \u003cAPI_URL\u003e       # For example: \u003cMS_URL\u003e/client/api\n  api-key = \u003cSERVICE_USER_API_KEY\u003e\n  secret-key = \u003cSERVICE_USER_SECRET_KEY\u003e\n  project-id = \u003cPROJECT_ID\u003e\n\nDelete the existing secret using kubectl and Kubernetes cluster config:\n   ./kubectl --kubeconfig kube.conf -n kube-system delete secret cloudstack-secret\n\nCreate a new secret using kubectl and Kubernetes cluster config:\n    ./kubectl --kubeconfig kube.conf -n kube-system create secret generic cloudstack-secret --from-file=/tmp/cloud-config\n\nRemove the temporary file:\n    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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache CloudStack: CKS cluster in project exposes user API keys","id":"CVE-2025-26521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"apache:cloudstack","products":["apache:cloudstack"],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Authentication Bypass Vulnerability in RupeeWeb trading platform","id":"CVE-2025-26522"},"packages":[],"prev":{"headline":"SQL injection in Cacti","id":"CVE-2025-26520"},"products":["Apache CloudStack"],"published":"2025-06-10","related":[{"cvss_score":10,"headline":"Missing authorization in n/a","id":"CVE-2012-4501","kev_date_added":null,"published":"2012-10-26"},{"cvss_score":9.8,"headline":"Apache CloudStack: Unauthenticated cluster service port leads to remote execution","id":"CVE-2024-38346","kev_date_added":null,"published":"2024-07-05"},{"cvss_score":9.8,"headline":"Apache CloudStack: Integration API service uses dynamic port when disabled","id":"CVE-2024-39864","kev_date_added":null,"published":"2024-07-05"},{"cvss_score":9.8,"headline":"Apache CloudStack: x-forwarded-for HTTP header parsed by default","id":"CVE-2024-29006","kev_date_added":null,"published":"2024-04-04"},{"cvss_score":9.8,"headline":"Apache CloudStack SAML Single Sign-On XXE","id":"CVE-2022-35741","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":9.8,"headline":"Command injection in Apache CloudStack","id":"CVE-2019-17562","kev_date_added":null,"published":"2020-05-14"},{"cvss_score":9.8,"headline":"Missing authorization in Apache CloudStack","id":"CVE-2016-6813","kev_date_added":null,"published":"2018-02-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Apache Software Foundation"]},"summary":"Project members can access the creator's API keys from Kubernetes cluster secrets, allowing account impersonation and resource compromise.","url":"https://insights.sbomify.com/CVE-2025-26521/"}