Description
Authorization Bypass Through User-Controlled Key vulnerability in elixir-grpc grpc allows authenticated attackers to access or modify resources belonging to other users by smuggling a conflicting value for any path-bound field via the query string or request body.
In 'Elixir.GRPC.Server.Transcode':map_request/5 (lib/grpc/server/transcode.ex), all three clauses use Map.merge/2 with path bindings as the first argument, giving them the lowest merge precedence. A request such as GET /users/me/profile?user_id=victim (or a POST with {"user_id": "victim"} when body: "*") yields a decoded protobuf struct where the path-bound field carries the attacker-supplied value rather than the router-extracted value. Any handler that uses the path-bound field for authorization, multi-tenancy scoping, or ownership checks is silently bypassed.
This issue affects grpc: from 0.8.0 before 1.0.0.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| elixir-grpc | grpc | 0.8.0 – < 1.0.0 | 1.0.0 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Hex | grpc | >= 0.8.0, < 1.0.0 | 1.0.0 | EEF-CVE-2026-48599 |
References
- https://github.com/elixir-grpc/grpc/security/advisories/GHSA-mwr4-5g34-j5cq vendor-advisory related
- EEF CNA record for CVE-2026-48599 related
- OSV record EEF-CVE-2026-48599 related
- Introducing commit 8aaf3d3 in elixir-grpc/grpc related
- Fix commit 33b6a09 in elixir-grpc/grpc patch