RHSA-2026:24506HighCVSS 9.1

Red Hat Security Advisory: OpenShift Container Platform 4.21 CNF IBU extras update

Published
June 8, 2026
Last Modified
July 27, 2026

🔗 CVE IDs covered (1)

CVE-2026-33186 →

📋 Description

CVE-2026-33186 — google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation

🎯 Affected products6

  • Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/lifecycle-agent-operator-bundle@sha256:efa3c43d1a9d17071d4c9eb7a72ad4bd214d9883f6f3a55dd3d580f61287fae5_amd64 as a component of Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/lifecycle-agent-rhel9-operator@sha256:628d2c96d02f8c4a883184d1b1a52f37be6ac8e77070d91f73dc9f288d2e117f_amd64 as a component of Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/lifecycle-agent-rhel9-operator@sha256:ea81cf0d4b173a2192f666b22f0b3f63de194ab9797bae080fcccef5aa35f80e_arm64 as a component of Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/recert-rhel9@sha256:46f13e24e9bebc355173950f3d372577e0de72bf5696d8e3e8290d04f40b6bde_amd64 as a component of Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/recert-rhel9@sha256:4d86beaefb1bd89fc4bcb3476e22f9c7c8fa76bced89ad9fe72e3d893319246a_arm64 as a component of Red Hat OpenShift Container Platform 4.21

✅ Remediation

For OpenShift Container Platform 4.21, see the following documentation for important instructions about upgrading your cluster and applying this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html/release_notes/index Information about accessing this content is available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/updating_clusters/index#updating-cluster-cli Workaround: To mitigate this issue, implement infrastructure-level normalization to ensure all incoming HTTP/2 `:path` headers are properly formatted with a leading slash before reaching the gRPC-Go server. This can be achieved by configuring a reverse proxy or API gateway to validate and normalize the `:path` header. Ensure that any such intermediary is properly configured and restarted to apply the changes, which may temporarily impact service availability.

🔗 References (4)