CVE-2026-84303: gRPC-Go: xDS RBAC HTTP Filter bypass via mixed-case Header Matching and gRFC A41 validation evasion
Summary A vulnerability in the xDS RBAC HTTP filter implementation in grpc-go allows remote attackers to bypass authorization policies (specifically DENY rules) by using mixed-case or canonical-case header matchers (e.g., X-Role instead of x-role). Additionally, the safety guards introduced by gRFC A41 to block grpc- prefixed headers can be evaded via variations in casing (e.g., Grpc-Status).
Published Sep 8, 2026
Affected packages
google.golang.org/grpc
- Ecosystem
- Go
- Affected
- <= 1.83.0
- Fixed in
- 1.83.1
- Check
go list -m google.golang.org/grpc
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A vulnerability in the xDS RBAC HTTP filter implementation in grpc-go allows remote attackers to bypass authorization policies (specifically DENY rules) by using mixed-case or canonical-case header matchers (e.g., X-Role instead of x-role). Additionally, the safety guards introduced by gRFC A41 to block grpc- prefixed headers can be evaded via variations in casing (e.g., Grpc-Status).
Impact
When an operator defines an RBAC policy referencing headers containing uppercase letters (e.g. X-Role), grpc-go fails to match incoming metadata keys because they are unconditionally lowercased. Because of this case-sensitivity mismatch, a policy designed to block requests containing specific header values fails open: the rule is evaluated as a non-match, and traffic that should have been rejected is served.
Furthermore, gRFC A41 requires rejecting configuration schemas specifying header matchers starting with grpc-. Because this check is executed case-sensitively in grpc-go, attackers can bypass the validation by specifying titles like Grpc-Status.
Patches
The problem is fixed in master and in the 1.83.1 release.
Credited to alimony.
References
- https://github.com/grpc/grpc-go/security/advisories/GHSA-qc2q-p7wx-3px3
- https://nvd.nist.gov/vuln/detail/CVE-2026-84303
- https://github.com/grpc/grpc-go/pull/9332
- https://github.com/grpc/grpc-go/pull/9335
- https://github.com/grpc/grpc-go/commit/db9482836c298f234c896cf82ab68cafc78237f8
- https://github.com/grpc/grpc-go/commit/ebba6f3f1b206e2b4dc4d1d5a96d18430302c2fe
- https://github.com/grpc/grpc-go/releases/tag/v1.83.1
- https://github.com/advisories/GHSA-qc2q-p7wx-3px3
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-84445
gRPC-Go xDS servers: Denial of Service (DoS) via crash due to missing `:authority` and `Host` headers
high8.7Sep 8, 2026CVE-2026-84304
gRPC-Go: Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation
high8.7Sep 1, 2026GHSA-hrxh-6v49-42gf
gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities
high8.8Jul 21, 2026CVE-2026-33186
gRPC-Go has an authorization bypass via missing leading slash in :path
critical9.1Mar 18, 2026GHSA-xr7q-jx4m-x55m
Private tokens could appear in logs if context containing gRPC metadata is logged in github.com/grpc/grpc-go
lowJul 5, 2024
