# CVE-2026-18947: Feast: feast: authorization bypass in /materialize endpoints enables dos via unauthorized full re-materialization

> An attacker can bypass authorization checks to trigger full re-materialization, causing denial of service via resource exhaustion.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-mvxh-8c54-7fwx

## What is CVE-2026-18947?

CVE-2026-18947 is a high-severity missing authorization vulnerability in Red Hat OpenShift AI (RHOAI), published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-18947?


## How do I fix CVE-2026-18947?

No fix has been published for CVE-2026-18947 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18947 being exploited?

There is no known exploitation of CVE-2026-18947 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-18947 and fix it if it is affected.

What it is: CVE-2026-18947 is a high-severity missing authorization vulnerability in Red Hat OpenShift AI (RHOAI), published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18947 in the wild and no public exploit code.

Affected product: Red Hat OpenShift AI (RHOAI). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-18947/ (Markdown: https://insights.sbomify.com/CVE-2026-18947/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18947
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18947
- OSV: https://osv.dev/vulnerability/CVE-2026-18947

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-18947/
Summaries are generated and may contain mistakes; the official description above is the record.