A vulnerability in Feast, as deployed in Red Hat OpenShift AI (RHOAI), allows an attacker to bypass authorization checks on the /materialize and /materialize-incremental endpoints by sending a specially crafted request that omits the feature_views field. This bypass enables an unauthenticated remote attacker (in default no_auth configurations) or any authenticated user to trigger a full re-materialization of all feature views. The resulting impact is a denial of service due to data corruption and significant resource consumption affecting all tenants. The vulnerability has a CVSS v3.1 score of 8.5, indicating high severity. The vendor advisory recommends restricting network access to trusted clients and enabling authentication mechanisms such as Kubernetes/OIDC to mitigate unauthenticated exploitation, although authenticated users can still trigger the denial of service.

The vulnerability allows bypassing intended authorization controls, enabling unauthorized triggering of a full re-materialization process. This leads to denial of service conditions caused by data corruption and excessive resource consumption across all tenants. Both unauthenticated attackers (if no authentication is configured) and authenticated users can exploit this flaw. There is no confidentiality impact, but integrity is highly impacted, and availability is affected at a low level due to denial of service.

Red Hat advises restricting network access to the Feast feature server to trusted clients using firewall rules or network policies. If the Feast server is configured with the default no_auth setting, enabling Kubernetes or OIDC authentication is recommended to require user authentication and prevent unauthenticated exploitation. However, because the authorization bypass still allows any authenticated user to trigger the denial of service, additional access controls or usage restrictions should be considered. No official patch or fix is currently confirmed; users should monitor the vendor advisory for updates.