Skip to main content
VulnerabilityPublished Updated

CVE-2026-18620: Red Hat OpenShift AI 2.25 · Insecure Direct Object Reference

Affects Red Hat OpenShift AI 2.25Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat OpenShift AI 2.25Affected–Fixed in–
Red HatRed Hat OpenShift AI 2.25Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.3Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.4Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.4Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.5Affected–Fixed in–

AI-suggested

Red Hat advises operators to configure an allow-list of ServiceAccounts that tenants can specify in their workflow run requests. Restricting the ServiceAccounts to a predefined, least-privileged set (e.g., the default 'pipeline-runner' only) prevents unauthorized privilege escalation. This configuration should be applied to the API server handling workflow run requests.

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.

References

Community reviews

Loading reviews…