Overly Permissive ClusterRole Allows Authenticated Users to Escalate Privileges to Cluster Admin
CVE: CVE-2025-10725
Component: openshift-ai
CWE: CWE-266
Severity: Important
CVSS v3: 9.6/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Release date: 2025-09-29T00:00:00+00:00

A flaw was found in Red Hat Openshift AI Service. A low-privileged attacker with access to an authenticated account, for example as a data scientist using a standard Jupyter notebook, can escalate their privileges to a full cluster administrator. This allows for the complete compromise of the cluster's confidentiality, integrity, and availability. The attacker can steal sensitive data, disrupt all services, and take control of the underlying infrastructure, leading to a total breach of the platform and all applications hosted on it.

Statement: Red Hat Security Ratings classify this as an Important and not Critical because it requires minimal authentication for the remote attacker to jeopardize an environment. Following https://access.redhat.com/security/updates/classification

Remediation:
For Red Hat OpenShift AI 2.16.3 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update:

https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
For Red Hat OpenShift AI 2.19.3 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update:

https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
For Red Hat OpenShift AI 2.21.1 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update:

https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
For Red Hat OpenShift AI 2.22.2 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update:

https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
For Red Hat OpenShift AI 2.24.0 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update:

https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
RHOAI versions 2.16.x

The recommended fix is to upgrade to version 2.16.3.
However, if Kueue features are not required, the Kueue component management state can be set to "Removed" in the RHOAI DataScienceCluster resource:

~~~
oc patch dsc default-dsc --type=merge -p='{"spec":{"components":{"kueue":{"managementState":"Removed"}}}}' -n redhat-ods-operator
~~~


RHOAI versions 2.19+

The recommended fix is to apply the available erratum.
Alternatively,  follow these steps:
1. Prevent the RHOAI operator from managing the kueue-batch-user-rolebinding by applying the necessary annotation:
~~~
oc patch clusterrolebinding kueue-batch-user-rolebinding -p '{"metadata":{"annotations": \{"opendatahub.io/managed":"false"}}}'
~~~

2. Disable the ClusterRoleBinding by updating its subject to a different, non-existent, group:
~~~
oc patch clusterrolebinding kueue-batch-user-rolebinding \
  -p '{
    "subjects": [
      {
        "kind": "Group",
        "name": "REPLACEME",
        "apiGroup": "rbac.authorization.k8s.io"
      }
    ]
  }'
~~~

It is important that the group used for the subject does not exist on the cluster to prevent the risk of unintentionally assigning these permissions to other non-privileged users.

3. Once updates providing fixes have been applied, it's recommended to remove the clusterrolebinding created in step 2 of the mitigation.
~~~
oc delete clusterrolebinding kueue-batch-user-rolebinding
~~~