Answer in brief
CVE-2025-12103 records a Medium severity (CVSS 5.0) vulnerability in Openshift-ai: trusty ai grants all authenticated users to list pods in any namespace. The current sources do not mark it as known exploited. The current feed maps Red Hat/rhoai/odh-trustyai-service-operator-rhel8 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/rhoai/odh-trustyai-service-operator-rhel8 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/rhoai/odh-trustyai-service-operator-rhel8generic | * | Not reported |
Published upstream
Oct 28, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
A flaw was found in Red Hat Openshift AI Service. The TrustyAI component is granting all service accounts and users on a cluster permissions to get, list, watch any pod in any namespace on the cluster. TrustyAI is creating a role `trustyai-service-operator-lmeval-user-role` and a CRB `trustyai-service-operator-default-lmeval-user-rolebinding` which is being applied to `system:authenticated` making it so that every single user or service account can get a list of pods running in any namespace on the cluster Additionally users can access all `persistentvolumeclaims` and `lmevaljobs`
Quoted source text, attributed separately from HOL analysis.