gh currently bundles google.golang.org/grpc at a version affected by CVE-2026-33186 — an authorization bypass caused by a missing leading slash in :path.
The server-side bypass doesn't apply to gh itself (it's a client, not a gRPC server), so this is not directly exploitable in gh's use case. However, image scanners flag gh binaries for this CVE, forcing downstream consumers to suppress it.
The fix is in grpc-go v1.79.3. Could a gh release be cut that picks up grpc-go >= 1.79.3?
Filed to track on our side — happy to share more context if helpful.
ghcurrently bundlesgoogle.golang.org/grpcat a version affected by CVE-2026-33186 — an authorization bypass caused by a missing leading slash in:path.The server-side bypass doesn't apply to
ghitself (it's a client, not a gRPC server), so this is not directly exploitable ingh's use case. However, image scanners flagghbinaries for this CVE, forcing downstream consumers to suppress it.The fix is in
grpc-go v1.79.3. Could aghrelease be cut that picks upgrpc-go >= 1.79.3?Filed to track on our side — happy to share more context if helpful.