Feast: feast-operator: feast: default authentication mode is no_auth — shared multi-tenant instances deployed without authentication
Summary
| CVE | CVE-2026-18941 |
|---|---|
| State | PUBLISHED |
| Assigner | redhat |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-10 21:17:20 UTC |
| Updated | 2026-08-11 05:17:13 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7.7 HIGH from [email protected]
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Problem Types: CWE-306 | CWE-306 Missing Authentication for Critical Function
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 7.7 | HIGH | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| 3.1 | CNA | CVSS | 7.7 | HIGH | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
ChangedConfidentiality
HighIntegrity
NoneAvailability
NoneCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Red Hat | Red Hat OpenShift AI 3.3 | unaffected 1786110033 * rpm | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift AI RHOAI | Not specified | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| bugzilla.redhat.com/show_bug.cgi | [email protected] | bugzilla.redhat.com | |
| access.redhat.com/security/cve/CVE-2026-18941 | [email protected] | access.redhat.com | |
| access.redhat.com/errata/RHSA-2026:53263 | [email protected] | access.redhat.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Additional Advisory Data
| Source | Time | Event |
|---|---|---|
| CNA | 2026-08-04T17:11:26.646Z | Reported to Red Hat. |
| CNA | 2026-08-10T18:51:18.348Z | Made public. |
Workarounds
CNA: 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.
There are currently no legacy QID mappings associated with this CVE.