CVE-2026-18947 json
Feast: feast: authorization bypass in /materialize endpoints enables dos via unauthorized full re-materialization
published 2026-08-10 2 mo ago modified 2026-10-19 21 d ago also EUVD-2026-55817
- cvss
- 8.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
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.
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 1791863220
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-18947 updated cvss 8.5
feast: Feast: Authorization bypass in /materialize endpoints enables DoS via unauthorized full re-materialization
-
Red Hat OpenShift AI 2.25 rhoai/odh-feature-server-rhel9 1786110051fixed: vendor fix RHSA-2026:53261
-
Red Hat OpenShift AI 3.3 rhoai/odh-feature-server-rhel9 1786110033fixed: vendor fix RHSA-2026:53263
-
Red Hat OpenShift AI 3.4 rhoai/odh-feature-server-rhel9 1791863220fixed: vendor fix RHSA-2026:84734
-
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-workbench-jupyter-pytorch-rocm-py312-rhel9, rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9, rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9, +7 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 1791869783, +99 morenot 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.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L |
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-862 Missing Authorization
References
-
access.redhat.com
/errata/RHSA-2026:53261
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:53263
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:84734
vendor-advisory
-
access.redhat.com
/security/cve/CVE-2026-18947
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2511164
issue-tracking
Sources
- CVE List CVE-2026-18947
- NVD CVE-2026-18947
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.