VulnerabilityPublished 10 Aug 2026Updated 19 Oct 2026

CVE-2026-18941: Red Hat OpenShift AI 2.25 · Missing Authentication

Affects Red Hat OpenShift AI 2.25Source CVE Database V5

Compare

Not known to be exploited · CVSS 7.7 High.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 60% 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:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

cwe-306

What to do

Affected software

Product	Affected	Fixed in
Red Hat OpenShift AI 2.25rhoai/odh-feature-server-rhel9	Affected–	Fixed in–
Red Hat OpenShift AI 3.3rhoai/odh-feature-server-rhel9	Affected–	Fixed in–
Red Hat OpenShift AI 3.4rhoai/odh-feature-server-rhel9	Affected–	Fixed in–
Red Hat OpenShift AI 3.4rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9	Affected–	Fixed in–
Red Hat OpenShift AI 3.4rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9	Affected–	Fixed in–
Red Hat OpenShift AI 3.4rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9	Affected–	Fixed in–

AI-suggested

Red Hat advises configuring Feast deployments to use Kubernetes RBAC authentication instead of the default 'no_auth' setting. FeatureStore Custom Resources (CRs) should explicitly specify an authentication mechanism other than 'no_auth'. For Feast SDK usage, avoid using 'no_auth' in production unless explicitly acknowledged with the environment variable 'FEAST_INSECURE_NO_AUTH=1'. These configuration changes require redeployment or restart of the affected Feast services.

Description

A flaw was found in Feast and feast-operator. The default configuration for both the Feast SDK and the feast-operator is "no_auth," meaning no security manager is installed. This default allows unauthenticated and unauthorized access to feature-server, registry-server, and offline-server endpoints. A remote attacker, by exploiting this missing authentication, could achieve remote code execution (RCE) by storing a malicious User-Defined Function (UDF) on the feature-server, trigger a denial of service (DoS) by forcing re-materialization of all tenant features, and gain unauthorized access to cross-tenant data.

Impact

The vulnerability allows an attacker with network access to the cluster to perform unauthenticated actions on critical Feast services. This can lead to remote code execution by uploading malicious UDFs, denial of service by forcing expensive re-materialization of features, and unauthorized access to sensitive data across tenants. The impact includes confidentiality breaches and potential privilege escalation within the affected environment. The CVSS v3.1 score is 7.7 (high severity) with network attack vector, low attack complexity, low privileges required, no user interaction, and scope changed. Confidentiality impact is high, with no integrity or availability impact reported.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Aug 2026, 21:13 UTC

Technical details

References

Community reviews

Related threats