CVE-2026-48599
Last modified
CVE-2026-48599 is a high-severity vulnerability rated 7.6/10 on the CVSS scale. 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. EPSS estimates a 0.27% chance of exploitation in the next 30 days.
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.
Metrics
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-48599?
How severe is CVE-2026-48599?
How do I fix CVE-2026-48599?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-48593Uncontrolled Resource Consumption vulnerability in oban-bg o…5.9
- CVE-2026-48594Improper Handling of Highly Compressed Data (Data Amplificat…8.2
- CVE-2026-48595Improper Handling of Case Sensitivity vulnerability in elixi…8.2
- CVE-2026-48596Improper Neutralization of CRLF Sequences in HTTP Headers ('…2.1
- CVE-2026-48597Allocation of Resources Without Limits or Throttling vulnera…8.2
- CVE-2026-48598Improper Encoding or Escaping of Output vulnerability in eli…2.1
- CVE-2026-4860A security flaw has been discovered in 648540858 wvp-GB28181…7.3
- CVE-2026-4861A weakness has been identified in Wavlink WL-NU516U1 260227.…8.8
- CVE-2026-48610Under certain network configurations, a malicious actor with…8.1
- CVE-2026-48611Improper authentication checks in the OAuth implementation a…9.8
- CVE-2026-48612Improper state verification in the OAuth implementation coul…8
- CVE-2026-48613SQL injection vulnerability in phpBB profile field migration…5.9
Are you affected by CVE-2026-48599?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
