PoC Monitor
← All CVEs
CVE-2025-10725published 30 Sep 2025 17:47 UTCData: JSON · API

Opendatahub-io opendatahub-operator

Openshift-ai: overly permissive clusterrole allows authenticated users to escalate privileges to cluster admin

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.

First public PoC 294 daysafter publication · 21 Jul 2026
Public PoCs11 on GitHub
CVSS9.9critical · scored by CNA · CWE-266
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

opendatahub-io opendatahub-operator
  • < 3.0.0

Fixed in 3.0.0

Red Hat Red Hat OpenShift AI 2.16

    Fixed in sha256:cebc8815e03b772343b15d0a7dce8fad6fcc71dd437d871db5a3691472350803

    Red Hat Red Hat OpenShift AI 2.19

      Fixed in sha256:43a8904396e55074ffb1afcfcd8fe6db0edcbc918a8ff8301b6b0920aea7eabf

      Red Hat Red Hat OpenShift AI 2.21

        Fixed in sha256:db339d2d4f86af4efa695ef193d19e26b25fec80017fa2780833a4cd944e383b

        Red Hat Red Hat OpenShift AI 2.22

          Fixed in sha256:dccc7c6cf920da7ffeadbad42f5727f2d58d54ceef399ac98441345d06ff10c4

          Red Hat Red Hat OpenShift AI 2.24

            Fixed in sha256:12c1d1066e75951aad1d333bcbc1675ba7a795b57744294c23decec1655709c7

            Mitigation

            Upgrade opendatahub-operator to 3.0.0 or later.

            Upgrade Red Hat OpenShift AI 2.16 to sha256:cebc8815e03b772343b15d0a7dce8fad6fcc71dd437d871db5a3691472350803 or later.

            Upgrade Red Hat OpenShift AI 2.19 to sha256:43a8904396e55074ffb1afcfcd8fe6db0edcbc918a8ff8301b6b0920aea7eabf or later.

            Upgrade Red Hat OpenShift AI 2.21 to sha256:db339d2d4f86af4efa695ef193d19e26b25fec80017fa2780833a4cd944e383b or later.

            Upgrade Red Hat OpenShift AI 2.22 to sha256:dccc7c6cf920da7ffeadbad42f5727f2d58d54ceef399ac98441345d06ff10c4 or later.

            Upgrade Red Hat OpenShift AI 2.24 to sha256:12c1d1066e75951aad1d333bcbc1675ba7a795b57744294c23decec1655709c7 or later.

            Workaround

            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 ~~~

            References

            4 more

            Timeline

            Days relative to CVE publication
            t=0+60+120+180+240CVE published30 Sep 2025 · t = 0First public PoC21 Jul 2026 · t+294d

            First public PoC 294 days after publication; not in CISA KEV. First PoC: kaiokmo/cve-2025-10725-eda-demo (created 21 Jul 2026, found by us: backfilled).

            PoC repositories

            Found on GitHub.

            1 PoCs

            PoCs 1
            RepositoryCreatedStarsAssessment
            kaiokmo/cve-2025-10725-eda-demo 21 Jul 2026 +294 d 0 PoC

            Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.