Skip to content
Fencer Vulns
high 7.7

CVE-2026-18941 json

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

published 2026-08-10 2 mo ago modified 2026-10-19 21 d ago also EUVD-2026-55815

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

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.

Patch / fix

  • Red Hat Red Hat OpenShift AI 2.25 1786110051
  • Red Hat Red Hat OpenShift AI 3.3 1786110033
  • Red Hat Red Hat OpenShift AI 3.4 1786107278, 1791833225, 1791868194, 1791868238

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-18941 updated cvss 7.7

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

  • Red Hat OpenShift AI 2.25 rhoai/odh-feature-server-rhel9 1786110051
    fixed: vendor fix RHSA-2026:53261
  • Red Hat OpenShift AI 3.3 rhoai/odh-feature-server-rhel9 1786110033
    fixed: vendor fix RHSA-2026:53263
  • Red Hat OpenShift AI 3.4 rhoai/odh-feature-server-rhel9 1786107278, rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9 1791868194, rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9 1791833225, rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9 1791868238
    fixed: vendor fix RHSA-2026:53262
  • Red Hat OpenShift AI (RHOAI) rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9, rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9, rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9, rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9, rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9, +4 more Red Hat OpenShift AI 2.25 rhoai/odh-rhel9-operator 1786112809, rhoai/odh-dashboard-rhel9 1785940823, rhoai/odh-operator-bundle 1786113363, rhoai/odh-caikit-nlp-rhel9 1785186995, rhoai/odh-ta-lmes-job-rhel9 1785187011, rhoai/odh-feast-operator-rhel9 1786110116, +19 more Red Hat OpenShift AI 3.3 rhoai/odh-trainer-rhel9 1785187865, rhoai/odh-rhel9-operator 1786129846, rhoai/odh-dashboard-rhel9 1786109683, rhoai/odh-operator-bundle 1786130475, rhoai/odh-ta-lmes-job-rhel9 1785187607, rhoai/odh-mod-arch-maas-rhel9 1786109736, +21 more Red Hat OpenShift AI 3.4 rhoai/odh-cli-rhel9 1791509689, rhoai/rhai-cli-rhel9 1791509689, rhoai/odh-automl-rhel9 1791535789, rhoai/odh-mlflow-rhel9 1791865967, rhoai/odh-autorag-rhel9 1791557539, rhoai/odh-trainer-rhel9 1784039162, +133 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.90% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected products

  • Red Hat Red Hat OpenShift AI 2.25
  • Red Hat Red Hat OpenShift AI 3.3
  • Red Hat Red Hat OpenShift AI 3.4
  • Red Hat Red Hat OpenShift AI (RHOAI)

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.