CVE-2026-18947High· 8.5▾ TwilightA flaw was found in Feast. An authorization bypass vulnerability exists in the /materialize and /materialize-incremental endpoints. By sending a specially crafted request that omits the feature_views field, an attacker can bypass intende…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 46.8 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.6%
A flaw was found in Feast. An authorization bypass vulnerability exists in the /materialize and /materialize-incremental endpoints. By sending a specially crafted request that omits the feature_views field, an attacker can bypass intended permission checks. This allows an unauthenticated remote attacker, or any authenticated user, to trigger a full re-materialization of all feature views. The consequence is a Denial of Service (DoS) due to data corruption and significant resource consumption across all tenants.
rhoai/odh-feature-server-rhel9 (all versions)rhoai/odh-feature-server-rhel9 (all versions)rhoai/odh-feature-server-rhel9 (all versions)rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
To mitigate this vulnerability, restrict network access to the Feast feature server to trusted clients only, using firewall rules or network policies. If the Feast feature server is configured with the default no_auth setting, enable Kubernetes/OIDC authentication to require user authentication for access. While enabling authentication will prevent unauthenticated exploitation, any authenticated user will still be able to trigger the denial of service due to the authorization bypass.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-18941High· 7.7Feast: feast-operator: feast: default authentication mode is no_auth — shared multi-tenant instances deployed without authentication
CVE-2026-18948Critical· 9.9A flaw was found in Feast
CVE-2026-103314High· 7.4Stackrox: stackrox: saml response replay allows multiple central authentication tokens
CVE-2026-112214Medium· 6.5Gstreamer1-plugins-ugly-free: gstreamer1-plugins-ugly-free: unbounded memory allocation in asfdemux simple index parser
CVE-2026-112210Medium· 6.0Rhc: rhc: local privilege escalation via symlink following in rhc-canonical-facts.service
CVE-2026-16460High· 7.4bootc: ostree: bootc/ostree: staged deployments not revalidated against container signature policy before finalization (CVE-2026-16460)