Possible fix(deps): 41 vulnerable dependencies in go.mod

This might be a false positive, but `go.mod` around line 1 looked worth a second pair of eyes.

CVE-2026-33186 is a CRITICAL authorization bypass vulnerability in google.golang.org/grpc <= v1.27.0. When HTTP/2 :path headers lack the mandatory leading slash (/), the gRPC server incorrectly routes requests in a way that causes path-based authorization interceptors to fail matching explicit deny rules. Attackers can exploit this by crafting malformed requests to bypass security policies and access restricted RPC endpoints, directly compromising access controls and system integrity. Risk Level: CRITICAL. Immediate remediation is required.

Something like this might fix it:

```diff
--- a/go.mod
+++ b/go.mod
@@ -1,4 +1,4 @@
module example.com/service

require (
- google.golang.org/grpc v1.27.0
+ google.golang.org/grpc v1.79.3
)

Apply via:
sed -i 's/google.golang.org/grpc v1.27.0/google.golang.org/grpc v1.79.3/' go.mod
go mod tidy
```

For reference: rule `CVE-2026-33186`. Rated critical.

I do not maintain this project, so I may well be missing context — if this is intentional or already handled elsewhere, please just close it.

---
*Found with automated scanning ([RedGem](https://code.redgem.net)) and reviewed before opening. If it is not useful, closing it is completely fine.*

Start with go.mod around line 1 and verify whether google.golang.org/grpc v1.27.0 is used and whether the reported CVE applies. Run go mod tidy after any dependency change; done means the dependency concern is resolved or confirmed as a false positive, with the reported vulnerable dependencies accounted for.

Written by the indexing model from the issue text.