CVE-2026-33186: gRPC gRPC-Go authorization bypass in HTTP/2 path validation

CVE-2026-33186 · Severity: critical · CVSS 9.1 · Published 2026-03-20

gRPC-Go is a popular framework used for high-performance communication between software services. A security flaw allows attackers to bypass access controls by sending specially formatted requests that omit a required leading slash. This could allow unauthorized users to access restricted data or perform actions they should not be permitted to do, particularly in environments that rely on specific 'deny' rules for security.

Technologies: google.golang.org/grpc (Go), Grpc. Vendors: Go, Grpc.

Quick answers

Is CVE-2026-33186 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33186 being exploited in the wild.
How severe is CVE-2026-33186?
Critical severity, with a CVSS score of 9.1, published 20 March 2026.
Which products and versions are affected?
google.golang.org/grpc (Go) SEMVER:introduced=0,fixed=1.79.3; gRPC-Go < 1.79.3.
Is there a fix for CVE-2026-33186?
Yes. google.golang.org/grpc (Go): upgrade to 1.79.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33186 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-33186?
Check whether you run google.golang.org/grpc (Go), Grpc or gRPC-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • google.golang.org/grpc (Go): upgrade to 1.79.3 or later
    go get google.golang.org/grpc@v1.79.3

Technical details

An authorization bypass exists in gRPC-Go due to improper input validation of the HTTP/2 ':path' pseudo-header. The server's routing logic was overly lenient, accepting paths that omitted the mandatory leading slash (e.g., 'Service/Method'). While the server correctly routed these requests, authorization interceptors (like grpc/authz) evaluated the raw, non-canonical string. If a security policy used 'deny' rules based on canonical paths (starting with '/') and had a fallback 'allow' rule, the malformed request would fail to match the deny rule and be permitted. This is exploitable by a remote attacker sending raw HTTP/2 frames. The vulnerability is fixed in version 1.79.3 by rejecting any path that does not begin with a leading slash.

Affected products

  • gRPC gRPC-Go < 1.79.3
  • Red Hat OpenShift Container Platform 4.19

Identifiers

  • CVE-2026-33186
  • GHSA-p77j-4mvh-x3m3
  • GO-2026-4762

Timeline

  • 2026-03-17: advisory: GitHub Advisory GHSA-p77j-4mvh-x3m3 published
  • 2026-03-20: disclosed: CVE-2026-33186 published to NVD
  • 2026-03-17: patched: Fixed in gRPC-Go version 1.79.3
  • 2026-04-29: advisory: Red Hat released security updates for OpenShift Container Platform

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.