Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
You can restrict Gateway access to some namespaces only. However, it does not prevent someone from an authorized namespace to hijack the traffic of another. Fully locking down access to the MaaS Gateway is a solution, however it defeats the self-service approach of the component.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 11 Aug 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Red Hat
Red Hat red Hat Openshift Ai (rhoai) |
|
| Vendors & Products |
Red Hat
Red Hat red Hat Openshift Ai (rhoai) |
Tue, 11 Aug 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 10 Aug 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in the Red Hat OpenShift AI (RHOAI) MaaS Gateway. Improper configuration of the Gateway in a model-serving context allows a standard user with low privileges to intercept, read, log, and alter all MaaS model traffic. This includes sensitive information such as access keys, input prompts, and outputs, leading to significant information disclosure and data tampering. | |
| Title | Rhoai maas: llm-d: maas/llm-d inference gateway: default allowedroutes.namespaces.from: all allows namespace users to hijack shared model-serving traffic (tokens, prompts, outputs) | |
| First Time appeared |
Redhat
Redhat openshift Ai |
|
| Weaknesses | CWE-284 | |
| CPEs | cpe:/a:redhat:openshift_ai | |
| Vendors & Products |
Redhat
Redhat openshift Ai |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-08-11T17:54:32.380Z
Reserved: 2026-06-29T14:05:37.264Z
Link: CVE-2026-13717
No data.
Status : Received
Published: 2026-08-10T21:17:19.343
Modified: 2026-08-10T21:17:19.343
Link: CVE-2026-13717
OpenCVE Enrichment
Updated: 2026-08-11T02:00:06Z