Skip to main content
VulnerabilityPublished Updated

CVE-2026-48599: grpc · Insecure Direct Object Reference

Affects grpcSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 1.0.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.0, 33b6a095dbc91c6dee3c7b90893d7d74952e82e4
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade grpc to 1.0.0; grpc to 33b6a095dbc91c6dee3c7b90893d7d74952e82e4.

Affected software

ProductAffectedFixed in
elixir-grpcgrpcAffected
  • >=0.8.0 <1.0.0
Fixed in
  • 1.0.0
elixir-grpcgrpcAffected
  • ≥ 8aaf3d3a8c4c7b08ac65e9c6f254e0d24da1d048, < 33b6a095dbc91c6dee3c7b90893d7d74952e82e4
Fixed in
  • 33b6a095dbc91c6dee3c7b90893d7d74952e82e4
Hexgrpcpkg:hex/grpcOther threatsAffected
  • >=0.8.0 <1.0.0
Fixed in
  • 1.0.0

CPE configurations (1)

  • cpe:2.3:a:elixir-grpc:grpc:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, avoid relying solely on path-bound fields for authorization decisions or implement additional validation to ensure these fields cannot be overridden by user-controlled input.

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.

References

Community reviews

Loading reviews…