Skip to main content
VulnerabilityPublished Updated

CVE-2026-18942: Red Hat OpenShift AI 2.25 · Code Injection

Affects Red Hat OpenShift AI 2.25Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 6 Nov 2026, 23:24 UTC

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

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 3.4Affected–Fixed in–
Red HatRed Hat OpenShift AI (RHOAI)Affected–Fixed in–

AI-suggested

Red Hat recommends configuring the Feast operator to use a dedicated, minimally-privileged ServiceAccount for the feast apply CronJob, ensuring that automountServiceAccountToken is set to false. Additionally, apply a restricted securityContext to the CronJob pod and implement network policies to restrict egress traffic to only necessary registry endpoints. Ensure that the CronJob ServiceAccount is separate from the feature-server ServiceAccount. These mitigations reduce the risk of privilege escalation by limiting the permissions and exposure of the automated process executing tenant code.

Description

A flaw was found in the Feast operator. A malicious tenant could inject arbitrary code into their feature repository. This code would be executed by an automated process with elevated privileges, allowing the tenant to steal sensitive credentials. This could lead to a direct escalation of privileges, granting the tenant administrative control over the Kubernetes cluster.

References

Community reviews

Loading reviews…