CVE-2026-13717: Improper Access Control
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.
AI Analysis
Technical Summary
The vulnerability in Red Hat OpenShift AI (RHOAI) MaaS Gateway arises from an insecure default configuration of allowedRoutes.namespaces.from, which permits any user in an authorized namespace to hijack shared model-serving traffic. This includes interception and alteration of sensitive information such as access keys, input prompts, and outputs. The issue is classified as improper access control (CWE-284). While restricting Gateway access to certain namespaces can mitigate risk, it does not prevent hijacking among authorized namespaces. Fully locking down access is a trade-off against the component's self-service design. The vulnerability has a CVSS v3.1 score of 8.8 (high severity) with network attack vector, low complexity, low privileges required, and no user interaction needed. No vendor-provided patch or official fix is currently available according to the advisory.
Potential Impact
An attacker with low privileges in any authorized namespace can intercept, read, log, and modify all model-serving traffic on the MaaS Gateway. This leads to significant confidentiality breaches (exposure of access keys and sensitive data), integrity violations (data tampering), and availability impact. The flaw compromises the security boundaries between namespaces, allowing unauthorized data access and manipulation within the shared model-serving environment.
Mitigation Recommendations
Currently, no official patch or fix is available. Mitigation involves restricting Gateway access to a limited set of namespaces; however, this does not prevent traffic hijacking among authorized namespaces. Fully locking down access to the MaaS Gateway can prevent exploitation but disables the self-service functionality of the component. Users should monitor the Red Hat advisory for updates on fixes and consider access restrictions as an interim measure.
CVE-2026-13717: Improper Access Control
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.
CVSS v3.1
Score 8.8high
Affected software
Red Hat
Red Hat OpenShift AI 3.4
Red Hat
Red Hat OpenShift AI 3.4
Red Hat
Red Hat OpenShift AI (RHOAI)
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Red Hat OpenShift AI (RHOAI) MaaS Gateway arises from an insecure default configuration of allowedRoutes.namespaces.from, which permits any user in an authorized namespace to hijack shared model-serving traffic. This includes interception and alteration of sensitive information such as access keys, input prompts, and outputs. The issue is classified as improper access control (CWE-284). While restricting Gateway access to certain namespaces can mitigate risk, it does not prevent hijacking among authorized namespaces. Fully locking down access is a trade-off against the component's self-service design. The vulnerability has a CVSS v3.1 score of 8.8 (high severity) with network attack vector, low complexity, low privileges required, and no user interaction needed. No vendor-provided patch or official fix is currently available according to the advisory.
Potential Impact
An attacker with low privileges in any authorized namespace can intercept, read, log, and modify all model-serving traffic on the MaaS Gateway. This leads to significant confidentiality breaches (exposure of access keys and sensitive data), integrity violations (data tampering), and availability impact. The flaw compromises the security boundaries between namespaces, allowing unauthorized data access and manipulation within the shared model-serving environment.
Mitigation Recommendations
Currently, no official patch or fix is available. Mitigation involves restricting Gateway access to a limited set of namespaces; however, this does not prevent traffic hijacking among authorized namespaces. Fully locking down access to the MaaS Gateway can prevent exploitation but disables the self-service functionality of the component. Users should monitor the Red Hat advisory for updates on fixes and consider access restrictions as an interim measure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-06-29T14:05:37.264Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-13717","vendor":"Red Hat"}]
Threat ID: 6a7a3b13bf8831d5398565e5
Added to database: 08/10/2026, 20:56:51 UTC
Last enriched: 08/10/2026, 21:26:15 UTC
Last updated: 09/23/2026, 01:47:41 UTC
Views: 53
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.