Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-12103

MEDIUM · 5.0 CVSS v3.1 Published 2025-10-28

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

56/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

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`

Technical summary

dbcve analysis · high confidence

The TrustyAI component in Red Hat OpenShift AI creates a Role (trustyai-service-operator-lmeval-user-role) and ClusterRoleBinding (trustyai-service-operator-default-lmeval-user-rolebinding) that is bound to system:authenticated, granting all users and service accounts on the cluster get, list, and watch permissions on pods in any namespace, plus access to all persistentvolumeclaims and lmevaljobs.

MitigationRestrict the ClusterRoleBinding to only grant access to specific authorized users or service accounts rather than all authenticated users, or remove the binding entirely if the permissions are not required.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

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

Am I affected?

dbcve checks

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

Check if TrustyAI or Red Hat Openshift AI is installed

Run 'oc get namespaces' or 'kubectl get namespaces' and look for namespaces like 'trustyai', 'openshift-ai', 'rhods' or check for installed operators with 'oc get operators' or 'kubectl get operators'

Affected if TrustyAI or Openshift AI operator is not installed - the CVE does not apply
Locate the ClusterRoleBinding

Run 'oc get clusterrolebinding trustyai-service-operator-default-lmeval-user-rolebinding' or 'kubectl get clusterrolebinding trustyai-service-operator-default-lmeval-user-rolebinding'

Affected if ClusterRoleBinding not found - the CVE does not apply (may have been patched or not yet deployed)
Inspect the ClusterRoleBinding subjects

Run 'oc get clusterrolebinding trustyai-service-operator-default-lmeval-user-rolebinding -o yaml' or 'kubectl get clusterrolebinding trustyai-service-operator-default-lmeval-user-rolebinding -o yaml' and examine the 'subjects' section

Affected if A subject with kind 'System:authenticated' or name 'system:authenticated' exists - this indicates the vulnerability is present
Review the granted permissions

In the same output, check the 'roleRef' section to identify the ClusterRole being referenced, then run 'oc get clusterrole <role-name> -o yaml' to view the actual permissions granted (get, list, watch on pods across all namespaces, access to persistentvolumeclaims and lmevaljobs)

Affected if The ClusterRole grants broad permissions across all namespaces to all authenticated users

Your environment is affected if the ClusterRoleBinding 'trustyai-service-operator-default-lmeval-user-rolebinding' exists and includes 'system:authenticated' as a subject, granting excessive cluster-wide permissions to every authenticated user.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Restrict the ClusterRoleBinding to only grant access to specific authorized users or service accounts rather than all authenticated users, or remove the binding entirely if the permissions are not required.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation3.0 h
Testing4.0 h
Review / QA2.0 h

13.0 hours of engineering $2,300

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-12103 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-12103?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 13 hrs · Moderate

Typical engagement from $2,300

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-12103 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References