Security readout for executives and security teams
Plain-English summary
A TrustyAI authorization error gives every authenticated OpenShift cluster user and service account visibility into pods across all namespaces, plus access to persistent volume claims and LMEvalJobs. This can expose workload and storage metadata useful for reconnaissance, especially in shared clusters. The supplied assessment reports no direct integrity or availability impact.
Executive priority
Schedule prompt remediation rather than emergency shutdown. Raise priority for multi-tenant clusters because any authenticated identity may enumerate workloads outside its namespace. Confirm ownership, affected builds, and remediation status; the supplied evidence does not establish active exploitation.
Technical view
TrustyAI creates trustyai-service-operator-lmeval-user-role and binds it through trustyai-service-operator-default-lmeval-user-rolebinding to system:authenticated. Consequently, low-privileged authenticated principals can get, list, and watch pods cluster-wide and access persistentvolumeclaims and lmevaljobs. Red Hat classifies this as CWE-266 with CVSS 3.1 score 5.0.
Likely exposure
Exposure exists where the cited affected Red Hat OpenShift AI 2.25, 3.0, or RHOAI TrustyAI packages are deployed and the generated binding targets system:authenticated. Exact version scope for the generic RHOAI entry is not provided. Exploitation requires an authenticated cluster identity, including a service account.
Exploitation context
The CVSS vector indicates network access, low privileges, low complexity, and no user interaction. The issue enables cross-namespace discovery and may reveal operational metadata. It is not listed as KEV, and the supplied sources provide no evidence of active exploitation or public weaponization.
Researcher notes
The scope change and confidentiality impact align with the supplied CVSS vector; integrity and availability are scored none. The bundle clearly identifies the unsafe subject and resources, but does not include corrected package versions, detailed PVC/LMEvalJob verbs, or exploitation telemetry. Avoid inferring access to volume contents from PVC access alone.
Mitigation direction
- Review Red Hat’s CVE page and both referenced RHSAs for the applicable corrected package or upgrade.
- Apply the Red Hat-supported remediation matching the deployed OpenShift AI release and TrustyAI package.
- After remediation, verify the TrustyAI binding no longer grants excessive access to system:authenticated.
- Prioritize shared clusters containing sensitive workloads or broadly issued user and service-account credentials.
Validation and detection
- Inventory deployed OpenShift AI releases and the listed TrustyAI package names and build identifiers.
- Inspect the named role binding and determine whether system:authenticated is currently a subject.
- Review the bound role rules for pods, persistentvolumeclaims, and lmevaljobs across namespaces.
- Using an authorized least-privileged test identity, confirm cross-namespace access is denied after remediation.
- Review audit records for unexpected cross-namespace requests by ordinary users or service accounts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-266: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-12103 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N3.11.4redhatVulnerability scoring details
Base CVSS 3.1 score
5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2025:21117CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:10184CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2025-12103CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2405966CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.