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).

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.

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.