RHSA-2026:24535HighCVSS 9.1

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

Published
June 8, 2026
Last Modified
September 8, 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.20
  • registry.redhat.io/openshift4/lifecycle-agent-operator-bundle@sha256:d58fcab5a50f6df010b50ca86346e082ce355f3ac4fa6f8dd1606a0522cbc743_amd64 as a component of Red Hat OpenShift Container Platform 4.20
  • registry.redhat.io/openshift4/lifecycle-agent-rhel9-operator@sha256:0c2894cb04a5cd4fbb0f944c946278a3921b1b9b88e6f82cfcf9d26594b595d1_arm64 as a component of Red Hat OpenShift Container Platform 4.20
  • registry.redhat.io/openshift4/lifecycle-agent-rhel9-operator@sha256:47db1a245c9f18162fb93e9fc9ae6513b7858a151c51bbd0d89b026e55d40f0d_amd64 as a component of Red Hat OpenShift Container Platform 4.20
  • registry.redhat.io/openshift4/recert-rhel9@sha256:7fbd77831e69c22e0c6a2bb310b25cd79fc4eeff30a5721e9ef84809937476c0_arm64 as a component of Red Hat OpenShift Container Platform 4.20
  • registry.redhat.io/openshift4/recert-rhel9@sha256:d05ff0fc7fbf384bfe09e461d0039921295935e26206e7b9ead58eb53086c3db_amd64 as a component of Red Hat OpenShift Container Platform 4.20

✅ Remediation

For OpenShift Container Platform 4.20, 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.20/html/release_notes/index Information about accessing this content is available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/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)