{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12103 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12103 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12103 is a medium-severity missing authorization vulnerability in Red Hat OpenShift AI (RHOAI), published on 28 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12103 and fix it if it is affected.\n\nWhat it is: CVE-2025-12103 is a medium-severity missing authorization vulnerability in Red Hat OpenShift AI (RHOAI), published on 28 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-12103 in the wild and no public exploit code.\n\nAffected product: Red Hat OpenShift AI (RHOAI). No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-12103/ (Markdown: https://insights.sbomify.com/CVE-2025-12103/index.md)","id":"CVE-2025-12103","markdown":"https://insights.sbomify.com/CVE-2025-12103/index.md","name":"CVE-2025-12103","record":{"aliases":["GHSA-hrh8-rvch-7hh9"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Red Hat OpenShift AI","requires_auth":"low_privilege","summary":"TrustyAI component incorrectly grants all authenticated users permission to list pods and access persistent volume claims across all namespaces.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"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.\n\nTrustyAI 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 \n\nAdditionally users can access all `persistentvolumeclaims` and `lmevaljobs`","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Openshift-ai: trusty ai grants all authenticated users to list pods in any namespace","id":"CVE-2025-12103","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Incorrect Content-Type Header","id":"CVE-2025-12104"},"packages":[],"prev":{"headline":"Cross-Site Scripting (XSS)","id":"CVE-2025-12101"},"products":["Red Hat OpenShift AI (RHOAI)","Red Hat OpenShift AI 2.25","Red Hat OpenShift AI 3.0"],"published":"2025-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-09","vendors":["Red Hat"]},"summary":"TrustyAI component incorrectly grants all authenticated users permission to list pods and access persistent volume claims across all namespaces.","url":"https://insights.sbomify.com/CVE-2025-12103/"}