RHSA-2026:22800HighCVSS 9.1

Red Hat Security Advisory: OpenShift Container Platform 4.21 CNF vRAN extras topology aware lifecycle manager update

Published
June 3, 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/topology-aware-lifecycle-manager-aztp-rhel9@sha256:3c360ca44835a7af1ef1ea4cbe803b5730bcadddfed2784b2d898efc10dc5c08_amd64 as a component of Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/topology-aware-lifecycle-manager-operator-bundle@sha256:9698159364350db7753c317c098ec008d73ab26796a7c400153b1a97607bc8c1_amd64 as a component of Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/topology-aware-lifecycle-manager-precache-rhel9@sha256:ca8caf9b82221f9e1229934f55f26ed65636cba7d732f3c5b66a1c7ebedb5b3f_amd64 as a component of Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/topology-aware-lifecycle-manager-recovery-rhel9@sha256:434fc75ae6d93dbffaca9aec0939e0540dc5ed9fd13c5a6c7ec979196708eb16_amd64 as a component of Red Hat OpenShift Container Platform 4.21
  • registry.redhat.io/openshift4/topology-aware-lifecycle-manager-rhel9-operator@sha256:9aee6301248bbbfba3858f4d16bc5084c59c299926f35df58a1c97658b828e44_amd64 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)