# CVE-2026-117574: A flaw was found in ai-gateway-payload-processing.


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-4c29-j43w-vg8g

## What is CVE-2026-117574?

CVE-2026-117574 is a critical vulnerability in Red Hat OpenShift AI (RHOAI), published on 28 Oct 2026. 

### Official description

A flaw was found in ai-gateway-payload-processing. An authenticated remote attacker can exploit this vulnerability by submitting a request specifying another tenant's model identifier in the request body or header. Because the service does not verify authorization before retrieving credentials from the shared store, it injects the target tenant's application programming interface (API) keys into the request. This flaw allows an attacker to perform unauthorized requests and consume another tenant's large language model (LLM) resources and quotas.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-117574 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117574 is a critical vulnerability in Red Hat OpenShift AI (RHOAI), published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117574 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-117574/ (Markdown: https://insights.sbomify.com/CVE-2026-117574/index.md)
```

## Sources

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

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