What is the CVSS score of CVE-2025-26521?

CVE-2025-26521 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.1%.

Which versions of Kubernetes are affected by CVE-2025-26521?

CVE-2025-26521 is a high-severity vulnerability (CVSS 8.1) affecting an unspecified product with a currently available patch.. A patch is available.

How to fix or mitigate CVE-2025-26521?

Within 24 hours: Identify all systems running the affected product and verify patch availability from the vendor. Within 7 days: Deploy vendor patch to non-production environments and conduct functional testing. Within 30 days: Complete patch deployment to all production systems, prioritizing internet-facing and critical infrastructure assets.

Kubernetes CVE-2025-26521

EUVD-2025-18065 HIGH

Information Exposure (CWE-200)

2025-06-10 security@apache.org

Privilege Escalation Apache Information Disclosure Kubernetes Cloudstack

8.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:40 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

4.19.3.0,4.20.1.0

EUVD ID Assigned

Mar 14, 2026 - 19:49 euvd

EUVD-2025-18065

Analysis Generated

Mar 14, 2026 - 19:49 vuln.today

CVE Published

Jun 10, 2025 - 23:15 nvd

HIGH 8.1

DescriptionCVE.org

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-<FIRST_EIGHT_CHARACTERS_OF_PROJECT_ID> First Name Kubernetes Last Name Service User Account Type 0 (Normal User) Role ID <ID_OF_SERVICE_ROLE>

Add the Service Account to the ProjectAdd this account to the project where the Kubernetes cluster(s) are hosted.
Generate API and Secret KeysGenerate API Key and Secret Key for the default user of this account.
Update the CloudStack Secret in the Kubernetes ClusterCreate a temporary file /tmp/cloud-config with the following data:

api-url = <API_URL>

For example: <MS_URL>/client/api

api-key = <SERVICE_USER_API_KEY> secret-key = <SERVICE_USER_SECRET_KEY> project-id = <PROJECT_ID>

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.