CVE-2026-18620: Data Science Pipelines · Insecure Direct Object Reference
Source GCVE Database
Not known to be exploited · CVSS 7.1 High : patch Red Hat OpenShift AI 2.25 soon.
Data as of 11 Nov 2026, 23:24 UTC
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 11 Nov 2026.
What to do
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat OpenShift AI 2.25 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift AI 2.25 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift AI 3.3 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift AI 3.4 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift AI 3.4 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift AI 3.5 | Affected– | Fixed in– |
AI-suggested
Red Hat has published security advisories (RHSA-2026:53261 and RHSA-2026:53262) for Red Hat OpenShift AI that include updated images and instructions for upgrading clusters to remediate this vulnerability. Users should follow the official Red Hat documentation to upgrade to the fixed versions of Red Hat OpenShift AI as soon as possible. No other specific mitigations are indicated. Patch status is confirmed by vendor advisories indicating updated images are available.
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
- nvd.nist.gov/vuln/detail/CVE-2026-18620 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:53261 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:53262 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:53263 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-18620 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2510320 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60520 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:65126 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:60367 (opens in a new tab)