/

CVE-2026-33186

Severity:

CRITICAL RISK

(9.1)

Authorization Bypass in gRPC-Go Servers

CVE-2026-33186

Modified

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-285, CWE-551

Impact:

Unauthorized Access to gRPC Methods

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

gRPC-Go servers prior to 1.79.3 contain an authorization bypass where malformed HTTP/2 :path pseudo-headers without a leading slash are routed to the correct handler but evaluated differently by path-based authorization logic.

When authorization interceptors enforce "deny" rules using canonical paths starting with /, requests using the non-canonical form (e.g., Service/Method) can evade those rules and be allowed by fallback "allow" policies.

Affected context

This vulnerability arises in gRPC-Go server deployments that:

  • Use gRPC-Go versions prior to 1.79.3, and
  • Rely on path-based authorization interceptors (such as google.golang.org/grpc/authz or custom interceptors using info.FullMethod or grpc.Method(ctx)), and
  • Define security policies with explicit "deny" rules for canonical paths (beginning with /) while permitting other requests via a fallback "allow" rule.

It is relevant when an attacker is able to send raw HTTP/2 frames directly to the gRPC server and control the :path pseudo-header, bypassing any intermediaries that might normalize or validate the path.

Exploit preconditions

  • Attack surface: Direct HTTP/2 interface of a gRPC-Go server (prior to 1.79.3), reachable over the network.
  • Required access: Ability to open a connection to the gRPC endpoint and send crafted HTTP/2 requests, including arbitrary :path values (e.g., via a custom HTTP/2 client or tooling that does not enforce canonical gRPC paths).
  • Trigger point: A request whose :path omits the leading slash (e.g., Service/Method instead of /Service/Method), targeting a method covered by a "deny" rule written only in canonical form.
  • Why exploitation is possible: The server's routing logic accepts both canonical and non-canonical paths, but authorization interceptors evaluate the raw path string. As a result, deny rules written for /Service/Method do not match Service/Method, and the request can fall through to a more permissive policy branch.

Why this happens

The underlying issue is inconsistent interpretation of the HTTP/2 :path pseudo-header between the core gRPC-Go routing layer and the authorization layer.

The routing component tolerates non-canonical method paths lacking a leading slash and still maps them to the correct service method.

However, authorization interceptors, including the official RBAC implementation (grpc/authz) and custom logic built on info.FullMethod or grpc.Method(ctx), rely on the raw path string for policy matching.

This discrepancy means that access control is evaluated against one representation of the method path while routing uses another, aligning with CWE-285: Improper Authorization, where an access control decision is made on incomplete or non-normalized input.

Potential impact

  • Unauthorized invocation of gRPC methods that are intended to be blocked by path-based "deny" rules.
  • Circumvention of RBAC or other policy frameworks relying on canonical gRPC method paths.
  • Exposure of sensitive operations or data to clients that should be restricted.
  • Potential elevation of privileges if protected administrative or internal-only methods are reachable via non-canonical paths.
  • In complex systems, possible lateral movement between services by calling blocked cross-service APIs.

General mitigation guidance

Effective mitigation focuses on ensuring consistent, canonical method paths for both routing and authorization, and on hardening policy evaluation:

  • Introduce a validating interceptor early in the server interceptor chain that rejects any request whose :path or method string does not conform to the canonical gRPC format (e.g., must start with / and match an expected pattern).
  • Normalize method paths inside authorization logic before rule evaluation, converting any variant representations to a single canonical form and rejecting inputs that cannot be safely normalized.
  • Design authorization policies to avoid relying solely on raw path strings where possible; instead, use structured method metadata (service name, method name, and possibly additional contextual attributes) when available.
  • Apply least-privilege defaults in RBAC policies, preferring explicit "allow" lists over broad fallback "allow" rules that permit unknown or mismatched paths.
  • Where feasible, ensure that upstream infrastructure (API gateways, proxies, or load balancers) verifies and normalizes gRPC :path values before forwarding them, or blocks malformed paths entirely.

How teams detect issues like this

Detection strategies typically involve examining both code and runtime behavior:

  • Static analysis & code review:
  • Search for gRPC-Go servers using path-based authorization, especially usage of google.golang.org/grpc/authz, interceptors referencing info.FullMethod, or helpers like grpc.Method(ctx) for policy decisions.
  • Flag policy code that compares raw path strings without canonicalization or validation.
  • Review interceptor ordering to ensure any validation or normalization occurs before authorization decisions.
  • Configuration and policy audits:
  • Inspect RBAC or custom authorization policies for deny rules that assume canonical paths (starting with /) combined with broad default allow behavior.
  • Identify any policies that treat unmatched paths as implicitly allowed.
  • Runtime monitoring and testing:
  • Use security testing tools or custom scripts to send gRPC requests with non-standard :path values (e.g., missing leading slash) and verify whether they are correctly rejected.
  • Analyze access logs for non-canonical method paths or unexpected method names being served successfully.
  • Automated code review and CI rules can be configured to detect use of unsafe path matching patterns and to enforce validation hooks for paths and methods.

Sources

SourceLink
github.comgithub.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10093
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10094
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10105
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10107
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10125
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10126
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10130
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10131
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10153
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10155
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10158
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10172
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10175
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10698
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10705
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10706
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11070
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11408
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11803
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11856
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11916
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11996
access.redhat.comaccess.redhat.com/errata/RHSA-2026:12116
access.redhat.comaccess.redhat.com/errata/RHSA-2026:12118
access.redhat.comaccess.redhat.com/errata/RHSA-2026:12119
access.redhat.comaccess.redhat.com/errata/RHSA-2026:12277
access.redhat.comaccess.redhat.com/errata/RHSA-2026:12279
access.redhat.comaccess.redhat.com/errata/RHSA-2026:12283
access.redhat.comaccess.redhat.com/errata/RHSA-2026:12337
access.redhat.comaccess.redhat.com/errata/RHSA-2026:13548
access.redhat.comaccess.redhat.com/errata/RHSA-2026:13791
access.redhat.comaccess.redhat.com/errata/RHSA-2026:13829
access.redhat.comaccess.redhat.com/errata/RHSA-2026:14775
access.redhat.comaccess.redhat.com/errata/RHSA-2026:15092
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17123
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17448
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17459
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17468
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17474
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17475
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17598
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17599
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17789
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18068
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18585
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19099
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19108
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19109
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19135
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19207
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19353
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19375
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19712
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19719
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19720
access.redhat.comaccess.redhat.com/errata/RHSA-2026:19721
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20034
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20035
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20041
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20042
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20088
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20089
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20322
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20436
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20943
access.redhat.comaccess.redhat.com/errata/RHSA-2026:20946
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21017
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21657
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21658
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21691
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21692
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21696
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21697
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21703
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21704
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21709
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21710
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21769
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21931
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21932
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22347
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22423
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22450
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22465
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22485
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22645
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22689
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22714
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22800
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22937
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22959
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22961
access.redhat.comaccess.redhat.com/errata/RHSA-2026:23228
access.redhat.comaccess.redhat.com/errata/RHSA-2026:23234
access.redhat.comaccess.redhat.com/errata/RHSA-2026:23235
access.redhat.comaccess.redhat.com/errata/RHSA-2026:23241
access.redhat.comaccess.redhat.com/errata/RHSA-2026:23246
access.redhat.comaccess.redhat.com/errata/RHSA-2026:23247
access.redhat.comaccess.redhat.com/errata/RHSA-2026:23345
access.redhat.comaccess.redhat.com/errata/RHSA-2026:24484
access.redhat.comaccess.redhat.com/errata/RHSA-2026:24506
access.redhat.comaccess.redhat.com/errata/RHSA-2026:24535
access.redhat.comaccess.redhat.com/errata/RHSA-2026:24536
access.redhat.comaccess.redhat.com/errata/RHSA-2026:24759
access.redhat.comaccess.redhat.com/errata/RHSA-2026:24853
access.redhat.comaccess.redhat.com/errata/RHSA-2026:24977
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25009
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25045
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25127
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25182
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25183
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25187
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25194
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25195
access.redhat.comaccess.redhat.com/errata/RHSA-2026:25201
access.redhat.comaccess.redhat.com/errata/RHSA-2026:26412
access.redhat.comaccess.redhat.com/errata/RHSA-2026:26413
access.redhat.comaccess.redhat.com/errata/RHSA-2026:26416
access.redhat.comaccess.redhat.com/errata/RHSA-2026:26420
access.redhat.comaccess.redhat.com/errata/RHSA-2026:26519
access.redhat.comaccess.redhat.com/errata/RHSA-2026:26568
access.redhat.comaccess.redhat.com/errata/RHSA-2026:26997
access.redhat.comaccess.redhat.com/errata/RHSA-2026:26999
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27001
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27004
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27063
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27076
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27712
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27856
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27892
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27893
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27901
access.redhat.comaccess.redhat.com/errata/RHSA-2026:27957
access.redhat.comaccess.redhat.com/errata/RHSA-2026:28047
access.redhat.comaccess.redhat.com/errata/RHSA-2026:28893
access.redhat.comaccess.redhat.com/errata/RHSA-2026:28964
access.redhat.comaccess.redhat.com/errata/RHSA-2026:29079
access.redhat.comaccess.redhat.com/errata/RHSA-2026:29082
access.redhat.comaccess.redhat.com/errata/RHSA-2026:29854
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34049
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34097
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34099
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34100
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34364
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34769
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34794
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34795
access.redhat.comaccess.redhat.com/errata/RHSA-2026:36611
access.redhat.comaccess.redhat.com/errata/RHSA-2026:36621
access.redhat.comaccess.redhat.com/errata/RHSA-2026:36651
access.redhat.comaccess.redhat.com/errata/RHSA-2026:36796
access.redhat.comaccess.redhat.com/errata/RHSA-2026:36882
access.redhat.comaccess.redhat.com/errata/RHSA-2026:37192
access.redhat.comaccess.redhat.com/errata/RHSA-2026:37275
access.redhat.comaccess.redhat.com/errata/RHSA-2026:37580
access.redhat.comaccess.redhat.com/errata/RHSA-2026:37585
access.redhat.comaccess.redhat.com/errata/RHSA-2026:40022
access.redhat.comaccess.redhat.com/errata/RHSA-2026:40030
access.redhat.comaccess.redhat.com/errata/RHSA-2026:40118
access.redhat.comaccess.redhat.com/errata/RHSA-2026:40792
access.redhat.comaccess.redhat.com/errata/RHSA-2026:40795
access.redhat.comaccess.redhat.com/errata/RHSA-2026:40945
access.redhat.comaccess.redhat.com/errata/RHSA-2026:40984
access.redhat.comaccess.redhat.com/errata/RHSA-2026:41019
access.redhat.comaccess.redhat.com/errata/RHSA-2026:41928
access.redhat.comaccess.redhat.com/errata/RHSA-2026:41941
access.redhat.comaccess.redhat.com/errata/RHSA-2026:41944
access.redhat.comaccess.redhat.com/errata/RHSA-2026:42049
access.redhat.comaccess.redhat.com/errata/RHSA-2026:42051
access.redhat.comaccess.redhat.com/errata/RHSA-2026:42150
access.redhat.comaccess.redhat.com/errata/RHSA-2026:42151
access.redhat.comaccess.redhat.com/errata/RHSA-2026:42240
access.redhat.comaccess.redhat.com/errata/RHSA-2026:42644
access.redhat.comaccess.redhat.com/errata/RHSA-2026:43225
access.redhat.comaccess.redhat.com/errata/RHSA-2026:43227
access.redhat.comaccess.redhat.com/errata/RHSA-2026:43253
access.redhat.comaccess.redhat.com/errata/RHSA-2026:43331
access.redhat.comaccess.redhat.com/errata/RHSA-2026:43692
access.redhat.comaccess.redhat.com/errata/RHSA-2026:44233
access.redhat.comaccess.redhat.com/errata/RHSA-2026:44235
access.redhat.comaccess.redhat.com/errata/RHSA-2026:47728
access.redhat.comaccess.redhat.com/errata/RHSA-2026:47952
access.redhat.comaccess.redhat.com/errata/RHSA-2026:48699
access.redhat.comaccess.redhat.com/errata/RHSA-2026:48790
access.redhat.comaccess.redhat.com/errata/RHSA-2026:50758
access.redhat.comaccess.redhat.com/errata/RHSA-2026:50843
access.redhat.comaccess.redhat.com/errata/RHSA-2026:51033
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53728
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53763
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53773
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53804
access.redhat.comaccess.redhat.com/errata/RHSA-2026:54191
access.redhat.comaccess.redhat.com/errata/RHSA-2026:54274
access.redhat.comaccess.redhat.com/errata/RHSA-2026:54286
access.redhat.comaccess.redhat.com/errata/RHSA-2026:54531
access.redhat.comaccess.redhat.com/errata/RHSA-2026:54757
access.redhat.comaccess.redhat.com/errata/RHSA-2026:56366
access.redhat.comaccess.redhat.com/errata/RHSA-2026:56431
access.redhat.comaccess.redhat.com/errata/RHSA-2026:56789
access.redhat.comaccess.redhat.com/errata/RHSA-2026:56854
access.redhat.comaccess.redhat.com/errata/RHSA-2026:56912
access.redhat.comaccess.redhat.com/errata/RHSA-2026:56959
access.redhat.comaccess.redhat.com/errata/RHSA-2026:57013
access.redhat.comaccess.redhat.com/errata/RHSA-2026:57365
access.redhat.comaccess.redhat.com/errata/RHSA-2026:59833
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60146
access.redhat.comaccess.redhat.com/errata/RHSA-2026:61245
access.redhat.comaccess.redhat.com/errata/RHSA-2026:6174
access.redhat.comaccess.redhat.com/errata/RHSA-2026:6428
access.redhat.comaccess.redhat.com/errata/RHSA-2026:6564
access.redhat.comaccess.redhat.com/errata/RHSA-2026:6802
access.redhat.comaccess.redhat.com/errata/RHSA-2026:7110
access.redhat.comaccess.redhat.com/errata/RHSA-2026:7128
access.redhat.comaccess.redhat.com/errata/RHSA-2026:7245
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8151
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8338
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8433
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8449
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8483
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8484
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8490
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8491
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8493
access.redhat.comaccess.redhat.com/errata/RHSA-2026:9385
access.redhat.comaccess.redhat.com/errata/RHSA-2026:9388
access.redhat.comaccess.redhat.com/errata/RHSA-2026:9440
access.redhat.comaccess.redhat.com/errata/RHSA-2026:9448
access.redhat.comaccess.redhat.com/errata/RHSA-2026:9453
access.redhat.comaccess.redhat.com/errata/RHSA-2026:9872
access.redhat.comaccess.redhat.com/security/cve/CVE-2026-33186
bugzilla.redhat.combugzilla.redhat.com/show_bug.cgi?id=2449833
security.access.redhat.comsecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33186.json

Frequently asked

questions

Yes. If a gRPC-Go server is reachable over the network and accepts direct HTTP/2 connections, an attacker with a suitable client can craft requests with non-canonical :path values to attempt to bypass path-based authorization policies.

The attacker needs network access to the gRPC endpoint and the ability to send low-level HTTP/2 requests, including arbitrary :path headers. No prior authentication is required beyond whatever the vulnerable service itself enforces.

The safest pattern is to ensure all requests are validated or normalized before any authorization logic runs. This includes rejecting paths that do not conform to canonical gRPC method format and making sure that both routing and authorization use the same canonical representation when making decisions.

To prevent similar problems, design access control layers to:

  • Operate on canonical, validated input rather than raw protocol fields.
  • Centralize normalization and validation in a shared interceptor or middleware that runs early in the request lifecycle.
  • Favor explicit allow-lists and least-privilege policies over permissive fallbacks.
  • Include tests and security reviews that cover edge cases in protocol handling, such as malformed or alternative path representations.
Find out what's already
exploitable in your codebase.