CVE-2026-13717Rhoai 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)
- 8.8HighCVSS base score
- 0.57%Exploitation in 30 daysEPSS · top 52% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By redhat
- 42 days later
· 42 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| redhatCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Awaiting Analysis | 3.1 | High8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.57% · top 52% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
llm-d
- affected < *
Red Hat · Red Hat OpenShift AI 3.4
- unaffected 1786123541 – < *
Red Hat · Red Hat OpenShift AI 3.4
- unaffected 1787153684 – < *
Red Hat · Red Hat OpenShift AI 3.4
- unaffected 1791468368 – < *
Red Hat · Red Hat OpenShift AI 3.4
- unaffected 1790958159 – < *
Red Hat · Red Hat OpenShift AI 3.4
- unaffected 1793001859 – < *
Red Hat · Red Hat OpenShift AI (RHOAI)
All versions: affected
What to do
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.
References
References6
- RHSA-2026:53262 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:60520 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:84734 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- RHSA-2026:92510 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-13717 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2494203 (opens in a new tab)issue-trackingx_refsource_REDHAT
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55807 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-13717)Record last updated .