Red Hat OpenShift AI Vulnerability Lets Attackers Seize Infrastructure Control
A vulnerability has been identified in the Red Hat OpenShift AI service, designated as CVE-2025-10725, which allows attackers with minimal access to escalate privileges and potentially take control of entire clusters.
A vulnerability has been identified in the Red Hat OpenShift AI service, designated as CVE-2025-10725, which allows attackers with minimal access to escalate privileges and potentially take control of entire clusters.
The vulnerability exists due to an overly permissive ClusterRole assignment. Users with low privileges, such as data scientists utilizing standard Jupyter notebook accounts, can exploit this vulnerability to gain full cluster administrator rights.
Once elevated, an attacker can access sensitive data, disrupt services, and control the underlying infrastructure, leading to a complete breach of both the platform and hosted applications.
CVE ID Affected Component CVSS v3.1 Score (Red Hat)
CVE-2025-10725 Red Hat OpenShift AI Service (rhoai/odh-rhel8-operator, rhoai/odh-rhel9-operator) 9.9 (Important)
The vulnerability exists due to an overly permissive ClusterRole assignment.
The flaw arises from a ClusterRoleBinding that connects the built-in system:authenticated group to the kueue-batch-user-role . This setup grants any authenticated user extensive job-creation rights across the cluster, potentially allowing malicious jobs to run with elevated privileges.
Administrators are advised to take the following actions to mitigate this issue:
Revoke the ClusterRoleBinding that associates kueue-batch-user-role with system:authenticated . Assign job-creation privileges only to specific users or groups that require them. Review other ClusterRoleBindings to ensure no other overly broad assignments exist.
These steps will help limit risk exposure and reduce the attack surface by confining administrative capabilities to trusted identities.
CVE-2025-10725 is documented on the CVE website and the NVD. Red Hat provides authoritative guidance on product-specific impacts and remediation measures.
This vulnerability highlights the dangers of overly permissive roles in Kubernetes environments. Regular auditing of roles and binding assignments, aligning permissions with job requirements, and enforcing strict separation between development, analytics, and administrative duties are recommended. Proactive cluster governance and vigilant permission management are crucial to preventing privilege escalation and ensuring the integrity of AI-powered platforms.
Based on reporting by GBHackers.
