CVE-2026-48599elixir-grpc grpc Authorization Bypass Through User-Controlled Key
NVD
Vulnerability Summary
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.
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.
CVSS v4.0 Base Metrics — Score 7.6 (HIGH)
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NAttack VectorNetwork
Attack ComplexityLow
Attack RequirementsPresent
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Affected & Patched Versions
- elixir-grpc grpc >= 0.8.0 and < 1.0.0
- elixir-grpc grpc >= 8aaf3d3a8c4c7b08ac65e9c6f254e0d24da1d048 and < 33b6a095dbc91c6dee3c7b90893d7d74952e82e4
- elixir-grpc grpc 1.0.0
- elixir-grpc grpc 33b6a095dbc91c6dee3c7b90893d7d74952e82e4
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run elixir-grpc grpc and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Jun 15, 2026Published
- Sep 24, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new elixir-grpc grpc CVEsYou are reading CVE-2026-48599. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore elixir-grpc grpc CVEs
External References
- Vendor Advisoryhttps://github.com/elixir-grpc/grpc/security/advisories/GHSA-mwr4-5g34-j5cq
- Referencehttps://cna.erlef.org/cves/CVE-2026-48599.html
- Referencehttps://osv.dev/vulnerability/EEF-CVE-2026-48599
- Patchhttps://github.com/elixir-grpc/grpc/commit/8aaf3d3a8c4c7b08ac65e9c6f254e0d24da1d048
- Patchhttps://github.com/elixir-grpc/grpc/commit/33b6a095dbc91c6dee3c7b90893d7d74952e82e4
Data last checked: Sep 23, 2026 10:57 UTC