What is the CVSS score of CVE-2026-13717?

CVE-2026-13717 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of OpenShift AI are affected by CVE-2026-13717?

A misconfiguration in Red Hat OpenShift AI's MaaS Gateway exposes organizations to internal man-in-the-middle attacks, allowing authenticated platform users to intercept and modify all model-serving…. A patch is available.

How to fix or mitigate CVE-2026-13717?

Within 24 hours: Audit RHOAI deployments to identify systems in production and assess exposure scope; establish monitoring for unauthorized traffic interception patterns. Within 7 days: Implement network microsegmentation to restrict model gateway access to authorized services only; rotate all API keys and credentials that transit RHOAI; document compensating controls and risk acceptance for continued operation. Within 30 days: Monitor Red Hat security advisories for patch availability; evaluate architectural alternatives (air-gapped deployments, third-party gateway hardening, or MaaS provider migration) if vendor patch timeline exceeds acceptable risk window.

OpenShift AI CVE-2026-13717

EUVD-2026-55807 HIGH

Improper Access Control (CWE-284)

2026-08-10 redhat

GHSA-335x-vvmj-55qx

Authentication Bypass Information Disclosure Red Hat Red Hat Openshift Ai Rhoai Red Hat

8.8

CVSS 3.1 · Vendor: redhat

Severity by source

Vendor (redhat) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

8.3 HIGH

PR:L confirmed by 'standard user with low privileges'; A:L rather than A:H as availability impact is not explicitly described in the advisory text.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Red Hat

8.8 HIGH

qualitative

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 10, 2026 - 21:34 vuln.today

CVE Published

Aug 10, 2026 - 20:44 nvd

HIGH 8.8

DescriptionCVE.org

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.

AnalysisAI

The MaaS (Model-as-a-Service) Gateway component in Red Hat OpenShift AI (RHOAI) is improperly configured, enabling any low-privileged authenticated user within the platform to act as a man-in-the-middle against all model-serving traffic. Affected users can intercept, read, log, and modify requests and responses traversing the gateway, exposing highly sensitive artifacts including API access keys, user input prompts, and model outputs. No public exploit code has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog, but the CVSS 8.8 rating with high confidentiality, integrity, and availability impact reflects the severity of unrestricted traffic access within a shared AI serving environment.

Technical ContextAI

Red Hat OpenShift AI (RHOAI) is an MLOps platform built on OpenShift Container Platform, providing a Model-as-a-Service (MaaS) gateway that proxies inference requests between consumers and hosted AI/ML models. The MaaS Gateway handles API traffic including authentication tokens and model I/O payloads. The root cause is CWE-284 (Improper Access Control): the gateway's access control policy is insufficiently restrictive, failing to isolate tenant traffic or enforce least-privilege boundaries for standard users. Affected products are captured in CPE cpe:2.3:a:red_hat:red_hat_openshift_ai_(rhoai):*:*:*:*:*:*:*:*, with the wildcard version field indicating that no specific bounded version range has been published by the vendor at time of analysis. The improper configuration flaw suggests a misconfiguration in gateway routing or proxy authorization policy rather than a memory-safety or injection issue.

RemediationAI

Consult the Red Hat security advisory at https://access.redhat.com/security/cve/CVE-2026-13717 for patch availability - no specific fixed version has been published in the input data, so a patched release version cannot be independently confirmed at this time. As a compensating control while awaiting a vendor patch, restrict RHOAI cluster access so that only trusted, vetted users are granted standard user roles on namespaces that host MaaS Gateway endpoints; this reduces the population of principals who could exploit the misconfiguration. Additionally, audit existing RHOAI RBAC policies and network policies to determine whether the MaaS Gateway is reachable to users outside intended serving namespaces, and apply namespace-level network isolation to limit gateway traffic scope. Rotate any API access keys that may have transited the MaaS Gateway in shared or multi-tenant environments as a precaution. Monitor the Red Hat Bugzilla entry (https://bugzilla.redhat.com/show_bug.cgi?id=2494203) for patch progression.