VulnerabilityPublished 30 Sep 2025Updated 24 Dec 2025

CVE-2025-10725: opendatahub-operator · Incorrect Privilege Assignment

Affects opendatahub-operatorSource CVE Database V5

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

9.9Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
opendatahub-io opendatahub-operator	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-10725, organizations should implement the following specific measures: 1) Immediately restrict access to the Red Hat Openshift AI Service and the opendatahub-operator to only trusted and essential personnel, enforcing the principle of least privilege. 2) Monitor and audit user activities within Jupyter notebook environments and the Openshift cluster to detect anomalous privilege escalations or suspicious behavior. 3) Apply any patches or updates provided by Red Hat as soon as they become available to address the privilege assignment flaw directly. 4) Employ multi-factor authentication (MFA) for all authenticated users to reduce the risk of compromised credentials being exploited. 5) Segment the network and isolate AI service clusters from other critical infrastructure to limit lateral movement in case of compromise. 6) Use role-based access control (RBAC) policies carefully, reviewing and tightening permissions assigned to users and service accounts. 7) Consider deploying runtime security tools that can detect and block privilege escalation attempts in Kubernetes environments. 8) Prepare incident response plans specifically for container and AI platform breaches to enable rapid containment and recovery. These targeted actions go beyond generic advice by focusing on access control, monitoring, patching, and containment strategies tailored to the Openshift AI service context.

Description

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.

Impact

The impact of CVE-2025-10725 is severe and far-reaching for organizations using Red Hat Openshift AI Service with the opendatahub-operator. Successful exploitation results in full cluster administrator privileges, enabling attackers to fully control the Kubernetes cluster environment. This can lead to unauthorized access to sensitive data, including intellectual property, customer information, and AI model data. Attackers can disrupt business-critical services by disabling or corrupting workloads, causing downtime and operational disruption. The attacker can also manipulate infrastructure components, potentially implanting persistent backdoors or launching further attacks within the network. The total compromise of confidentiality, integrity, and availability can damage organizational reputation, lead to regulatory compliance violations, and incur significant financial losses. Given the increasing adoption of Openshift for AI and container orchestration workloads, the vulnerability threatens a broad range of industries including technology, finance, healthcare, and government sectors. The ease of exploitation by authenticated users makes insider threats or compromised accounts particularly dangerous. The lack of known exploits in the wild currently provides a window for remediation, but the critical severity demands immediate attention to prevent potential attacks.

References

Community reviews

Loading reviews…