{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-18620 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18620 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18620 is a high-severity vulnerability in Red Hat OpenShift AI 2.25, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18620 and fix it if it is affected.\n\nWhat it is: CVE-2026-18620 is a high-severity vulnerability in Red Hat OpenShift AI 2.25, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-18620 in the wild and no public exploit code.\n\nAffected product: Red Hat OpenShift AI 2.25. 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-2026-18620/ (Markdown: https://insights.sbomify.com/CVE-2026-18620/index.md)","id":"CVE-2026-18620","markdown":"https://insights.sbomify.com/CVE-2026-18620/index.md","name":"CVE-2026-18620","record":{"aliases":["GHSA-g68c-wmxr-x3rh"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["privilege_escalation","data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenShift AI","requires_auth":"low_privilege","summary":"A restricted user can specify a privileged ServiceAccount to bypass authorization, enabling privilege escalation, secret disclosure, and command execution in other pods.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"A flaw was found in Data Science Pipelines. A restricted user, or tenant, can exploit an improper authorization vulnerability in the setDefaultServiceAccount function. By specifying a more privileged ServiceAccount (SA) during a CreateRun request, an attacker can bypass authorization checks. This allows the tenant to run their containers with elevated privileges, potentially leading to the disclosure of sensitive information (secrets) and the ability to execute commands within other users' pods.","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":"Data-sciences-pipeline: user-controlled serviceaccount for workflow pods without authorization check — confused deputy","id":"CVE-2026-18620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Data-sciences-pipeline: dsp: v1 argo template path accepts arbitrary workflow spec, bypassing all v2 security hardening","id":"CVE-2026-18621"},"packages":[],"prev":{"headline":"Ml-metdata: bundled grpc 1.46.3 (2022) with published http/2 dos cves — directly reachable on listener","id":"CVE-2026-18618"},"products":["Red Hat OpenShift AI 2.25","Red Hat OpenShift AI 3.3","Red Hat OpenShift AI 3.4","Red Hat OpenShift AI 3.5"],"published":"2026-08-10","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-09-21","vendors":["Red Hat"]},"summary":"A restricted user can specify a privileged ServiceAccount to bypass authorization, enabling privilege escalation, secret disclosure, and command execution in other pods.","url":"https://insights.sbomify.com/CVE-2026-18620/"}