How to verify and secure configuration of OpenShift AI Gateway for Model Serving

Solution In Progress - Updated -

Issue

Gateway API listener configurations using allowedRoutes.namespaces.from: All allow any namespace on the cluster to attach HTTPRoutes to the corresponding hostname managed by the Gateway.
This enables route hijack attacks: a user with standard namespace-level permissions can create an HTTPRoute that intercepts traffic intended for a legitimate model endpoint. Intercepted traffic includes API keys, user prompts, and model responses. The attack requires no elevated privileges and produces no visible errors for legitimate users.
Previous versions of Red Hat OpenShift AI documentation and upstream examples used this insecure default.

Environment

Red Hat OpenShift AI Self-Managed 3.x (3.3, 3.4)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content