CVE-2026-18941

Feast: feast-operator: feast: default authentication mode is no_auth — shared multi-tenant instances deployed without authentication

Published Aug 10, 2026 CVSS 3.1 · 7.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A flaw in Feast and feast-operator reduces the default authentication mode to no_auth, meaning no security manager is installed and all endpoints are left unprotected. This permits an attacker to access the feature-server, registry-server, and offline-server endpoints without authentication or authorization. The vulnerability can lead to remote code execution by uploading a malicious User-Defined Function (UDF) to the feature-server, cause a denial of service by forcing re‑materialization of all tenant features, and expose cross‑tenant data, which matches CWE-306 (Authentication bypass).

Affected Systems

The affected environment is Red Hat OpenShift AI (RHOAI) deployments that include Feast. Any version of RHOAI that hosts Feast without an explicit authentication mechanism is vulnerable. No specific version range is listed by Red Hat, so all current releases that use the default no_auth configuration may be impacted.

Risk and Exploitability

The CVSS score of 7.7 indicates high severity, and although EPSS is not available, the lack of authentication makes exploitation straightforward over the network when the vulnerable endpoints are exposed. This is not listed in the CISA KEV catalog, but the risk remains high because an attacker can use public API endpoints to upload malicious code and trigger denial‑of‑service or data‑exposure attacks. The attack vector is therefore remote via the HTTP/HTTPS interfaces of Feast services, with no special access prerequisites other than the ability to reach those endpoints.

Remediation

Vendor Workaround

To mitigate this vulnerability, configure Feast deployments to utilize Kubernetes RBAC authentication. Ensure that `FeatureStore` Custom Resources (CRs) explicitly define an authentication mechanism other than `no_auth`. For Feast SDK usage, avoid the `no_auth` setting in production environments unless `FEAST_INSECURE_NO_AUTH=1` is explicitly set, acknowledging the security implications. Applying these configuration changes will require a redeployment or restart of the affected Feast services.


OpenCVE Recommended Actions

  • Update all FeatureStore custom resources in the cluster to specify an authentication mechanism other than no_auth, such as Kubernetes RBAC.
  • Redeploy or restart the Feast services after applying the configuration changes to ensure the new authentication settings take effect.
  • In any Feast SDK configuration, remove the no_auth setting; if leaving it enabled accept the risk by setting the environment variable FEAST_INSECURE_NO_AUTH=1 only after documenting the rationale.

Generated by OpenCVE AI on August 10, 2026 at 22:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:/a:redhat:openshift_ai:2.25::el9
cpe:/a:redhat:openshift_ai:3.4::el9
References
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Red Hat
Red Hat red Hat Openshift Ai (rhoai)
Vendors & Products Red Hat
Red Hat red Hat Openshift Ai (rhoai)
Type Values Removed Values Added
CPEs cpe:/a:redhat:openshift_ai:3.3::el9
References
Type Values Removed Values Added
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.
Title Feast: feast-operator: feast: default authentication mode is no_auth — shared multi-tenant instances deployed without authentication
First Time appeared Redhat
Redhat openshift Ai
Weaknesses CWE-306
CPEs cpe:/a:redhat:openshift_ai
Vendors & Products Redhat
Redhat openshift Ai
References
Metrics cvssV3_1

{'score': 7.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N'}

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Oct 19, 2026, 11:10 AM
Reserved
Aug 5, 2026, 1:24 PM
Status
Awaiting Analysis
Published
Aug 10, 2026, 9:17 PM
Modified
Oct 19, 2026, 12:17 PM
Severity
Important
Public date
Aug 10, 2026, 6:51 PM