OpenShift AI 3.4.3 bundles a Critical security update with operational fixes
The asynchronous update lists 20 CVEs and repairs failures in vLLM inference, model serving, pipelines and dashboard access.
Red Hat issued OpenShift AI 3.4.3 on August 11 as a Critical security advisory. The advisory lists 20 CVEs and publishes updated OpenShift AI images across amd64, arm64, ppc64le and s390x.
What changed
The 3.4 resolved-issues notes describe 3.4.3 as an asynchronous errata release carrying security updates, bug fixes and enhancements.
The operational fixes extend beyond the security payload. Red Hat says 3.4.3 prevents vLLM from terminating on IBM Z when an inference request explicitly includes the temperature field. It also restores the ability to stop models served through the Distributed Inference Server with llm-d runtime from the OpenShift AI dashboard.
Other resolved problems include missing Feast certificates and a service in the default configuration, runtime-image lists that did not populate for the first workbench in a namespace, and model deployments whose hardware-profile tolerations, node selectors or identifiers were not injected into the underlying InferenceService.
Who it affects
The security advisory applies to Red Hat OpenShift AI. The resolved-issues list is especially relevant to teams operating vLLM on IBM Z, llm-d-backed distributed inference, Feast feature stores, Elyra pipelines, and model-serving workloads scheduled through hardware profiles.
Platform teams should also note fixes for dashboard access through standard OpenShift routes and for clusters that already run Argo Workflows alongside Data Science Pipelines.
What to do
Administrators should review RHSA-2026:53262, identify the affected OpenShift AI 3.4 deployments, and follow Red Hat’s linked product documentation for the upgrade procedure. Because Red Hat rates the advisory Critical, this is an update to schedule through the normal security-change process rather than defer as a routine feature patch.
After updating, teams with affected workflows should verify vLLM requests that set temperature, llm-d model stop operations, Feast SDK access from workbenches, and hardware-profile scheduling. Those checks map directly to the failures Red Hat lists as resolved in the 3.4.3 notes.
sources
- RHSA-2026:53262 — RHOAI 3.4.3 security advisoryaccess.redhat.com
- Red Hat OpenShift AI 3.4 resolved issuesdocs.redhat.com
comments · 0