{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-6193 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6193 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6193 is a medium-severity command injection vulnerability in Red Hat OpenShift AI (RHOAI), published on 20 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-6193 and fix it if it is affected.\n\nWhat it is: CVE-2025-6193 is a medium-severity command injection vulnerability in Red Hat OpenShift AI (RHOAI), published on 20 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-6193 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-6193/ (Markdown: https://insights.sbomify.com/CVE-2025-6193/index.md)","id":"CVE-2025-6193","markdown":"https://insights.sbomify.com/CVE-2025-6193/index.md","name":"CVE-2025-6193","record":{"aliases":["GHSA-wppx-2c2r-43hc"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Red Hat OpenShift AI","requires_auth":"high_privilege","summary":"Attackers with CR deployment permissions can execute arbitrary commands in LMEvalJob pods via crafted custom resources in TrustyAI Explainability.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"A command injection vulnerability was discovered in the TrustyAI Explainability toolkit. Arbitrary commands placed in certain fields of a LMEValJob custom resource (CR) may be executed in the LMEvalJob pod's terminal. This issue can be exploited via a maliciously crafted LMEvalJob by a user with permissions to deploy a CR.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Trustyai-explainability: command injection via lmevaljob cr","id":"CVE-2025-6193","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Direct Request ('Forced Browsing') in GitLab","id":"CVE-2025-6195"},"packages":[],"prev":{"headline":"Use after free in Chrome","id":"CVE-2025-6192"},"products":["Red Hat OpenShift AI (RHOAI)","Red Hat OpenShift AI 2.16"],"published":"2025-06-20","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":"Attackers with CR deployment permissions can execute arbitrary commands in LMEvalJob pods via crafted custom resources in TrustyAI Explainability.","url":"https://insights.sbomify.com/CVE-2025-6193/"}