gRPC-Go rejects HTTP/2 paths without a leading slash
AffectsgRPC-Go servers using path-based authorization with canonical-path deny rules and a fallback allow rule
Before the upgrade, a raw HTTP/2 request with a :path lacking a leading slash could reach its handler while evading canonical-path deny rules. The updated server rejects that path with codes.Unimplemented before authorization interceptors or handlers run.
Show release-note lines
* **security:** update module google.golang.org/grpc to v1.79.3 [security] ([#1907](https://github.com/open-feature/flagd/issues/1907)) ([ad51d4e](https://github.com/open-feature/flagd/commit/ad51d4e8fe0570474c824273983f54b3ca38b083))github.com/open-feature/flagd/releases/tag/flagd/v0.14.4