{"answers":{"affected":"3 open source packages ship an affected version, including grpc.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48599 exists.","fix":"Upgrade grpc to 1.0.0 or later.","what":"CVE-2026-48599 is a high-severity authentication bypass vulnerability in elixir-grpc grpc, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48599 and fix it if it is affected.\n\nWhat it is: CVE-2026-48599 is a high-severity authentication bypass vulnerability in elixir-grpc grpc, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48599 exists.\n\nAffected packages and fixed versions:\n- grpc (Hex): affected from 0.8.0; fixed in 1.0.0\n- grpc (Hex): affected from 0.8.0; fixed in 1.0.0\n- grpc (Hex): affected from 0.8.0; fixed in 1.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-48599/ (Markdown: https://insights.sbomify.com/CVE-2026-48599/index.md)","id":"CVE-2026-48599","markdown":"https://insights.sbomify.com/CVE-2026-48599/index.md","name":"CVE-2026-48599","record":{"aliases":["EEF-CVE-2026-48599","GHSA-mwr4-5g34-j5cq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir gRPC library","requires_auth":"low_privilege","summary":"Authenticated attackers can bypass authorization checks in Elixir gRPC services by overriding path-bound fields via query strings or request bodies.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.\n\nIn '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.\n\nThis issue affects grpc: from 0.8.0 before 1.0.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Authorization bypass via path binding override in elixir-grpc/grpc HTTP transcoding","id":"CVE-2026-48599","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":5,"next":{"headline":"Missing authorization in EFG","id":"CVE-2026-48610"},"packages":[{"ecosystem":"Hex","fixed":["1.0.0"],"introduced":["0.8.0"],"last_affected":[],"package":"grpc","purl":"pkg:hex/grpc","source":"EEF-CVE-2026-48599"},{"ecosystem":"Hex","fixed":["1.0.0"],"introduced":["0.8.0"],"last_affected":[],"package":"grpc","purl":null,"source":"GHSA-mwr4-5g34-j5cq"},{"ecosystem":"Hex","fixed":["1.0.0"],"introduced":["0.8.0"],"last_affected":[],"package":"grpc","purl":"pkg:hex/grpc","source":"GHSA-mwr4-5g34-j5cq"}],"prev":{"headline":"CRLF injection in Tesla.Multipart disposition parameters allows multipart part header injection","id":"CVE-2026-48598"},"products":["grpc"],"published":"2026-06-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["elixir-grpc"]},"summary":"Authenticated attackers can bypass authorization checks in Elixir gRPC services by overriding path-bound fields via query strings or request bodies.","url":"https://insights.sbomify.com/CVE-2026-48599/"}