Fedora Account System
Red Hat Associate
Red Hat Customer
gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:10107 https://access.redhat.com/errata/RHSA-2026:10107
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:10706 https://access.redhat.com/errata/RHSA-2026:10706
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:10705 https://access.redhat.com/errata/RHSA-2026:10705
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:19135 https://access.redhat.com/errata/RHSA-2026:19135
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:19207 https://access.redhat.com/errata/RHSA-2026:19207
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:19353 https://access.redhat.com/errata/RHSA-2026:19353
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2026:18068 https://access.redhat.com/errata/RHSA-2026:18068
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:19719 https://access.redhat.com/errata/RHSA-2026:19719
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2026:19721 https://access.redhat.com/errata/RHSA-2026:19721
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:19720 https://access.redhat.com/errata/RHSA-2026:19720
This issue has been addressed in the following products: Cryostat 4 on RHEL 9 Via RHSA-2026:17789 https://access.redhat.com/errata/RHSA-2026:17789
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2026:20322 https://access.redhat.com/errata/RHSA-2026:20322
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2026:20436 https://access.redhat.com/errata/RHSA-2026:20436
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:22450 https://access.redhat.com/errata/RHSA-2026:22450
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:22714 https://access.redhat.com/errata/RHSA-2026:22714
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:22937 https://access.redhat.com/errata/RHSA-2026:22937
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:23228 https://access.redhat.com/errata/RHSA-2026:23228
This issue has been addressed in the following products: Red Hat Satellite 6.16 for RHEL 8 Red Hat Satellite 6.16 for RHEL 9 Via RHSA-2026:27076 https://access.redhat.com/errata/RHSA-2026:27076
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:27712 https://access.redhat.com/errata/RHSA-2026:27712
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:27856 https://access.redhat.com/errata/RHSA-2026:27856
This issue has been addressed in the following products: Red Hat OpenStack Platform 17.1 for RHEL 9 Via RHSA-2026:28047 https://access.redhat.com/errata/RHSA-2026:28047
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2026:26997 https://access.redhat.com/errata/RHSA-2026:26997
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2026:26999 https://access.redhat.com/errata/RHSA-2026:26999
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2026:29079 https://access.redhat.com/errata/RHSA-2026:29079