RHSA-2026:10107HighCVSS 9.1

Red Hat Security Advisory: rhc security update

Published
April 23, 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 products14

  • Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-1:0.2.5-6.el8_10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-1:0.2.5-6.el8_10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-1:0.2.5-6.el8_10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-1:0.2.5-6.el8_10.src as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-1:0.2.5-6.el8_10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-debuginfo-1:0.2.5-6.el8_10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-debuginfo-1:0.2.5-6.el8_10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-debuginfo-1:0.2.5-6.el8_10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-debuginfo-1:0.2.5-6.el8_10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-debugsource-1:0.2.5-6.el8_10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-debugsource-1:0.2.5-6.el8_10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-debugsource-1:0.2.5-6.el8_10.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • rhc-debugsource-1:0.2.5-6.el8_10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, 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)