Am I affected?
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.
Weaknesses & attack patterns
Weakness
CWE-639
·
Authorization Bypass Through User-Controlled Key
in catalog →
MITRE ↗
Attack patterns
CAPEC-460
·
HTTP Parameter Pollution (HPP)
MITRE ↗
Affected — Hex / grpc Hex.pm ↗ Repository ↗
modules · source files · routines
Affected — GitHub / elixir-grpc/grpc Repository ↗
modules · source files · routines
Configurations
References
GHSA-mwr4-5g34-j5cq ↗
vendor-advisory
EEF-CVE-2026-48599 ↗
related
Credits
CVSS breakdown
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N