CVE-2026-18942: Vulnerability in Red Hat Red Hat OpenShift AI 2.25
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.
AI Analysis
Technical Summary
CVE-2026-18942 is a vulnerability in the Feast operator component of Red Hat OpenShift AI (RHOAI). A malicious tenant can inject arbitrary Python code into their feature repository, which is then executed by the feast apply CronJob using the feature-server's ServiceAccount permissions. This execution context allows the attacker to access the ServiceAccount token and escalate privileges to cluster-admin level, potentially gaining full administrative control over the Kubernetes cluster. The vulnerability is due to the feast apply CronJob running untrusted code with elevated privileges. Red Hat advises configuring the Feast operator to use a dedicated, minimally-privileged ServiceAccount with automountServiceAccountToken disabled, applying restricted security contexts to the CronJob pod, and limiting network egress to required registry endpoints.
Potential Impact
The vulnerability allows a malicious tenant to execute arbitrary code with elevated privileges within the Kubernetes cluster, leading to theft of sensitive credentials and escalation to cluster-admin privileges. This can result in full administrative control over the Kubernetes environment, posing a significant security risk to the cluster and its workloads.
Mitigation Recommendations
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.
CVE-2026-18942: Vulnerability in Red Hat Red Hat OpenShift AI 2.25
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.
CVSS v3.1
Score 5.5medium
Affected software
Red Hat
Red Hat OpenShift AI 2.25
Red Hat
Red Hat OpenShift AI 3.4
Red Hat
Red Hat OpenShift AI (RHOAI)
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-18942 is a vulnerability in the Feast operator component of Red Hat OpenShift AI (RHOAI). A malicious tenant can inject arbitrary Python code into their feature repository, which is then executed by the feast apply CronJob using the feature-server's ServiceAccount permissions. This execution context allows the attacker to access the ServiceAccount token and escalate privileges to cluster-admin level, potentially gaining full administrative control over the Kubernetes cluster. The vulnerability is due to the feast apply CronJob running untrusted code with elevated privileges. Red Hat advises configuring the Feast operator to use a dedicated, minimally-privileged ServiceAccount with automountServiceAccountToken disabled, applying restricted security contexts to the CronJob pod, and limiting network egress to required registry endpoints.
Potential Impact
The vulnerability allows a malicious tenant to execute arbitrary code with elevated privileges within the Kubernetes cluster, leading to theft of sensitive credentials and escalation to cluster-admin privileges. This can result in full administrative control over the Kubernetes environment, posing a significant security risk to the cluster and its workloads.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-08-05T13:25:36.192Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-18942","vendor":"Red Hat"}]
Threat ID: 6a7a3b16bf8831d539856682
Added to database: 08/10/2026, 20:56:54 UTC
Last enriched: 08/10/2026, 21:13:13 UTC
Last updated: 09/24/2026, 13:47:43 UTC
Views: 48
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.