dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-10725

CRITICAL · 9.9 CVSS v3.1 Published 2025-09-30
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A privilege escalation vulnerability in Red Hat Openshift AI Service allows a low-privileged authenticated user with standard data scientist access (e.g., Jupyter notebook) to gain full cluster administrator privileges, compromising the entire Kubernetes cluster.

MitigationApply vendor-provided patches for Openshift AI and review RBAC policies to ensure non-admin users cannot access cluster-level resources through the AI service interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Openshift AI version
    Run 'oc get deployment -n redhat-ods-appmesh' or check the operator version in OperatorHub to find the installed Openshift AI version
    Affected if The installed version is unpatched and falls within the vulnerable version range for CVE-2025-10725
  2. Verify standard data scientist user access
    Check if low-privileged users have access to the Openshift AI service interface, particularly Jupyter notebook functionality. Use 'oc get users' and 'oc get groups' to enumerate accessible identities
    Affected if Standard data scientist users (non-admin) can authenticate to Openshift AI service
  3. Review Jupyter notebook service account permissions
    Inspect the service account used by Jupyter notebooks in the AI service namespace. Run 'oc get serviceaccount -n <ai-service-namespace>' and check associated role bindings
    Affected if Jupyter notebook service accounts have elevated cluster permissions or can access cluster-scoped resources
  4. Audit cluster role bindings for AI service users
    Run 'oc get clusterrolebindings' and search for bindings that grant cluster-admin or elevated privileges to users or groups associated with the AI service
    Affected if Non-admin users or service accounts from the AI service have cluster-admin or escalated cluster-level permissions
  5. Check for unexpected privilege escalation paths
    Review RBAC policies to verify if the AI service can create or modify Kubernetes resources at cluster scope. Examine 'oc auth can-i' capabilities for standard data scientist users
    Affected if Standard data scientist users can perform cluster-level operations they should not have access to

Your environment is affected if Openshift AI is running with a vulnerable version and low-privileged data scientist users have the ability to escalate to cluster administrator privileges through the AI service interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Apply vendor-provided patches for Openshift AI and review RBAC policies to ensure non-admin users cannot access cluster-level resources through the AI service interface.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10725 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data