Skip to main content
VulnerabilityPublished Updated

CVE-2026-18608: CWE-250

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-18608· High 8.7

Not known to be exploited · CVSS 8.7 High : patch Red Hat OpenShift AI 2.25 soon.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/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 10 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 has issued security advisories for Red Hat OpenShift AI that include this vulnerability and recommends upgrading to the latest available versions following their official documentation. Although no explicit patch or fix is stated for CVE-2026-18608 alone, users should apply the updated images and follow Red Hat's upgrade instructions to mitigate the risk.

Description

A flaw was found in the Data Science Pipelines Operator (DSPO). The operator's ClusterRole, which defines its permissions, includes extensive privileges beyond what is necessary for its operation. These excessive permissions, such as the ability to execute commands within pods and manage cluster-wide roles, could be exploited. If the DSPO pod were compromised, an attacker could leverage these privileges to gain full administrative control over the entire Kubernetes cluster.

References

Community reviews

Loading reviews…