CVE-2026-18941
HighCVSS 7.7Exploitation Probability (EPSS)
Low risk45th percentile - higher than 45% of all known CVEs
Summary
A vulnerability in Feast and feast-operator is due to the default 'no_auth' configuration, which installs no security manager. This allows unauthenticated and unauthorized access to feature-server, registry-server, and offline-server endpoints. A remote attacker can exploit the missing authentication to achieve remote code execution (RCE) by storing a malicious UDF, trigger DoS by forcing re-materialization, and gain unauthorized access to cross-tenant data.
Risk Assessment
Lack of authentication enables remote code execution, DoS attacks, and breach of data isolation between tenants, posing a critical security threat.
Recommendation
Configure Feast and feast-operator with authentication and authorization enabled, and update to a patched version.
Original NVD description (English source)
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.