Auth bypass in Elixir-Grpc Grpc
CVE-2026-48599
- CVSS
- Not scored
- Public exploits
- None known
- EPSS
- 0.003 · 27.8th percentile
- Published
- 2026-06-15
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.
Vulnerability class: IDOR (Insecure Direct Object Reference)
Published · last modified .
EPSS exploit prediction
EPSS 0.003, 27.8th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Elixir-Grpc Grpc — versions 0.8.0, 8aaf3d3a8c4c7b08ac65e9c6f254e0d24da1d048
Weakness classification (CWE)
References
- github.com/elixir-grpc/grpc/security/advisories/GHSA-mwr4-5g34-j5cq (related, vendor-advisory)
- EEF CNA record for CVE-2026-48599 (related)
- OSV record EEF-CVE-2026-48599 (related)
- Fix commit 33b6a09 in elixir-grpc/grpc (patch)
- Introducing commit 8aaf3d3 in elixir-grpc/grpc (related)