RHSA-2026:53804HighCVSS 9.1

Red Hat Security Advisory: OpenShift Virtualization v4.16 Images

Published
August 11, 2026
Last Modified
August 11, 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 products7

  • Red Hat Container Native Virtualization 4.16
  • registry.redhat.io/container-native-virtualization/aaq-controller-rhel9@sha256:4988e8a7db4524568c2ac31569dd6fba455e62f5eca2eb0ec341ec04f12bab1f_amd64 as a component of Red Hat Container Native Virtualization 4.16
  • registry.redhat.io/container-native-virtualization/aaq-controller-rhel9@sha256:75ab642244e0f1d4d02d27e9e93fa2835e473bcd75f90afcd1c4ac80d1068586_arm64 as a component of Red Hat Container Native Virtualization 4.16
  • registry.redhat.io/container-native-virtualization/aaq-operator-rhel9@sha256:1fd1982cd924e70edd42d40fd0838494b5777fe865874bd5487f98e59c741b13_amd64 as a component of Red Hat Container Native Virtualization 4.16
  • registry.redhat.io/container-native-virtualization/aaq-operator-rhel9@sha256:af33ad17e71131ee027b29106410ef6b77e5c5bb9be9ffab84b184f7d323c7b8_arm64 as a component of Red Hat Container Native Virtualization 4.16
  • registry.redhat.io/container-native-virtualization/aaq-server-rhel9@sha256:506ea70975ca36350c956850d6e3a87e1d59fad1aa3aa80b1468bfe0fcccf979_amd64 as a component of Red Hat Container Native Virtualization 4.16
  • registry.redhat.io/container-native-virtualization/aaq-server-rhel9@sha256:554f1b28e2aa74a3001687dd8b5b9fd36b5bac5be20176cecf151d8e009b7d26_arm64 as a component of Red Hat Container Native Virtualization 4.16

✅ Remediation

Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 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)