Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Privilege Escalation in Red Hat OpenShift AI Service

IdentifiersCVE-2025-10725CWE-266· Incorrect Privilege Assignment

CVE-2025-10725 is a privilege escalation vulnerability in Red Hat OpenShift AI Service caused by incorrect privilege assignment in the platform's RBAC configuration. According to the provided content, the ClusterRole "kueue-batch-user-role" is incorrectly bound to the "system:authenticated" group, which grants any authenticated entity, including low-privileged user workbench or notebook service accounts, permission to create OpenShift Jobs in any namespace. A low-privileged authenticated user, such as a data scientist using a standard Jupyter notebook, can exploit this by creating a malicious job in a privileged namespace, causing it to run under a higher-privilege ServiceAccount, exfiltrating that token, and pivoting to cluster-admin level access. The described attack path can ultimately lead to root access on cluster master nodes and full cluster takeover.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in complete compromise of the affected OpenShift AI cluster. An attacker can escalate from a minimally privileged authenticated account to cluster administrator, access all cluster resources and secrets, steal sensitive data, modify or delete workloads, disrupt or shut down services, and compromise the confidentiality, integrity, and availability of the platform and hosted applications. The provided content further indicates the attack path may extend to root access on cluster master nodes, enabling control of the underlying infrastructure.

Mitigation

If you can’t patch tonight, do this now.

As an immediate mitigation, remove the binding between "kueue-batch-user-role" and "system:authenticated" to prevent arbitrary authenticated users from creating Jobs across namespaces. Restrict job-creation rights to only required users or service accounts, enforce least-privilege RBAC for Jupyter notebook and workbench environments, and avoid granting broad permissions to system-level groups. Because the vulnerability enables full environment takeover, the provided content also supports treating exposed clusters as potentially compromised: review audit logs for suspicious Job creation, privileged namespace activity, unexpected ServiceAccount token use, and signs of lateral movement or master-node access.

Remediation

Patch, then assume compromise.

Apply Red Hat's security update for CVE-2025-10725 when available for the affected OpenShift AI deployment. Based on the provided content, remediation includes correcting the RBAC misconfiguration by removing the ClusterRoleBinding that links the "kueue-batch-user-role" ClusterRole to the "system:authenticated" group and replacing it with narrowly scoped permissions granted only to explicitly authorized principals on an as-needed basis. Validate that no broad job-creation permissions remain assigned to system-level groups and review notebook/workbench service account privileges for least-privilege compliance.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity32

Community discussion across Reddit, Mastodon, and other social sources.