Skip to content
Threat Brief

← All advisories

CVE-2026-124278

High 7.6No known exploitationFix available

Path bindings ignored for gRPC Content-Types on transcoded routes in elixir-grpc grpc_server

Record last updated

CVSS score

7.6

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 43% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Authorization Bypass Through User-Controlled Key vulnerability in elixir-grpc grpc_server and grpc allows an attacker to make a handler act on a resource other than the one named in the URL of an HTTP-transcoded route, via a request with a gRPC Content-Type. Only the transcoding clause of GRPC.Server.do_handle_request/4 (grpc_server/lib/grpc/server.ex, and lib/grpc/server.ex before the package split) applies the route's path bindings to the request message. The Cowboy handler picks that clause from the request Content-Type, not from the route. A request to a transcoded URL with application/grpc or application/grpc-web is decoded from the body alone, so every path-bound field takes its value from the body. A gateway, proxy rule or WAF that authorizes on the URL path sees one resource while the handler receives another. This issue affects grpc: from 0.8.0 before 1.0.0; grpc_server: from 1.0.0 before 1.1.0.

Weakness: CWE-436, CWE-639

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
elixir-grpcgrpcfrom 0.8.0 before 1.0.01.0.0CVE Program
elixir-grpcgrpcfrom 8aaf3d3a8c4c7b08ac65e9c6f254e0d24da1d048 before 0332faae5f5e132314794dbfdae5edecbccea2920332faae5f5e132314794dbfdae5edecbccea292CVE Program
elixir-grpcgrpc_serverfrom 0332faae5f5e132314794dbfdae5edecbccea292 before 953ab980d8a127e895d3ab9505fc4b9337bb32f7953ab980d8a127e895d3ab9505fc4b9337bb32f7CVE Program
elixir-grpcgrpc_serverfrom 1.0.0 before 1.1.01.1.0CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references