Vulnerability · Published Mar 20, 2026 · Assigned by GitHub_M
CVE-2026-33186gRPC-Go has an authorization bypass via missing leading slash in :path
Critical 9.1
In plain English
A critical-severity security flaw in grpc-go from grpc. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 1.6% (higher than 76% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code. Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:10 | opentelemetry-collector | 0.144.0-2.el10_2 | ALSA-2026:19135 |
| AlmaLinux:9 | opentelemetry-collector | 0.144.0-2.el9_8 | ALSA-2026:19353 |
| AlmaLinux:8 | osbuild-composer | 101.5-1.el8_10.alma.1 | ALSA-2026:48790 |
| AlmaLinux:8 | osbuild-composer-core | 101.5-1.el8_10.alma.1 | ALSA-2026:48790 |
| AlmaLinux:8 | osbuild-composer-worker | 101.5-1.el8_10.alma.1 | ALSA-2026:48790 |
| Alpine:v3.24 | rclone | 1.73.5-r0 | ALPINE-CVE-2026-33186 |
| Debian:12 | golang-google-grpc | no fix listed | DEBIAN-CVE-2026-33186 |
| Debian:13 | golang-google-grpc | no fix listed | DEBIAN-CVE-2026-33186 |
| Debian:14 | golang-google-grpc | 1.79.3-1 | DEBIAN-CVE-2026-33186 |
| Go | google.golang.org/grpc | 1.79.3 | GHSA-p77j-4mvh-x3m3 |
| Go | google.golang.org/grpc | 1.79.3 | GO-2026-4762 |
| Rocky Linux:10 | image-builder | 0:52.1-1.el10_2.rocky.0.1 | RLSA-2026:22937 |
| Rocky Linux:9 | image-builder | 0:52.1-1.el9_8 | RLSA-2026:23228 |
| Rocky Linux:10 | opentelemetry-collector | 0:0.144.0-2.el10_2 | RLSA-2026:19135 |
| Rocky Linux:9 | opentelemetry-collector | 0:0.144.0-2.el9_8 | RLSA-2026:19353 |
| Rocky Linux:10 | osbuild-composer | 0:165.1-2.el10_2.rocky.0.1 | RLSA-2026:22450 |
| Rocky Linux:8 | osbuild-composer | 0:101.5-1.el8_10.rocky.0.6 | RLSA-2026:48790 |
| Rocky Linux:9 | osbuild-composer | 0:165.1-2.el9_8.rocky.0.1 | RLSA-2026:22714 |
| Ubuntu:22.04:LTS | golang-google-grpc | no fix listed | UBUNTU-CVE-2026-33186 |
| Ubuntu:25.10 | golang-google-grpc | no fix listed | UBUNTU-CVE-2026-33186 |
| Ubuntu:26.04:LTS | golang-google-grpc | no fix listed | UBUNTU-CVE-2026-33186 |
| Ubuntu:26.10 | golang-google-grpc | no fix listed | UBUNTU-CVE-2026-33186 |
| Ubuntu:22.04:LTS | google-guest-agent | no fix listed | UBUNTU-CVE-2026-33186 |
| Ubuntu:24.04:LTS | google-guest-agent | no fix listed | UBUNTU-CVE-2026-33186 |
| Ubuntu:25.10 | google-guest-agent | no fix listed | UBUNTU-CVE-2026-33186 |
| Ubuntu:26.04:LTS | google-guest-agent | no fix listed | UBUNTU-CVE-2026-33186 |
| Ubuntu:26.10 | google-guest-agent | no fix listed | UBUNTU-CVE-2026-33186 |
Affected products (as reported)
Weakness: CWE-285, CWE-551 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
- https://github.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3 x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-33186 vdb-entry, x_refsource_REDHAT
- RHBZ#2449833 issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33186.json x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:41019 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:54191 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:54757 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:43225 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:29079 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:34097 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:26997 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:27076 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:17789 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:36796 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:28047 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:20436 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:18068 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:20322 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:26999 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:42150 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:42151 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:42240 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:19719 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:27856 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:22937 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:19135 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:22450 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:48790 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:10107 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:61245 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:56959 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:19721 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:19720 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:27712 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:10705 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:10706 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:23228 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:19353 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:22714 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:19207 vendor-advisory, x_refsource_REDHAT