CVE-2026-124278: Path bindings ignored for gRPC Content-Types on transcoded routes in elixir-grpc grpc_server
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.49% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: elixir-grpc grpc 0332faae5f5e132314794dbfdae5edecbccea292, 1.0.0; elixir-grpc grpc_server 1.1.0, 953ab980d8a127e895d3ab9505fc4b9337bb32f7.
Low priority for now. Upgrade to elixir-grpc grpc 0332faae5f5e132314794dbfdae5edecbccea292, 1.0.0; elixir-grpc grpc_server 1.1.0, 953ab980d8a127e895d3ab9505fc4b9337bb32f7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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_server: from 1.0.0 before 1.1.0; grpc: from 0.8.0 before 1.0.0.
- Published
- Nov 13, 2026
- Updated
- Nov 13, 2026
- EPSS
- 0.4% · 43th percentile
- CWE
- CWE-436
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · EEF
- 7.6
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (EEF). Independent of NVD's CPE analysis and usually ahead of it.
elixir-grpc grpc
- 0.8.0 and later · before 1.0.0affected · semver
- 8aaf3d3a8c4c7b08ac65e9c6f254e0d24da1d048 and later · before 0332faae5f5e132314794dbfdae5edecbccea292affected · git
elixir-grpc grpc_server
- 1.0.0 and later · before 1.1.0affected · semver
- 0332faae5f5e132314794dbfdae5edecbccea292 and later · before 953ab980d8a127e895d3ab9505fc4b9337bb32f7affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Hex | grpc | from 0.8.0 · before 1.0.0 | 1.0.0 |
| Hex | grpc_server | from 1.0.0 · before 1.1.0 | 1.1.0 |
Same product
elixir-grpc: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-124279Streaming request body limit enforced only after an 8 MB read in elixir-grpc grpc_server32Monitor
- CVE-2026-121809CPU exhaustion via a truncated gRPC message on streaming RPCs in elixir-grpc grpc_server32Monitor
- CVE-2026-71397Unbounded request body accumulation on streaming RPCs causes memory exhaustion in grpc_server32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-123635Nov 13, 2026 · Refused calls drain the HTTP/2 connection flow-control window in elixir-grpc grpc_server25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| elixir-grpc grpc | 0332faae5f5e132314794dbfdae5edecbccea292 | Vendor (CNA) |
| elixir-grpc grpc | 1.0.0 | Vendor (CNA) |
| elixir-grpc grpc_server | 1.1.0 | Vendor (CNA) |
| elixir-grpc grpc_server | 953ab980d8a127e895d3ab9505fc4b9337bb32f7 | Vendor (CNA) |
| Hex:grpc | 1.0.0 | Package registry (OSV) |
| Hex:grpc_server | 1.1.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+1 d
- TodayNov 16, 2026+3 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Eurico Nicacioreporter
- Paulo Valenteremediation developer
- Peter Ullrichcoordinator
- Jonatan Männchen / EEFcoordinator
Not on record for this CVE: variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-436 · Interpretation ConflictCVSS 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/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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/elixir-grpc/grpc/commit/0332faae5f5e132314794dbfdae5edecbccea292
- github.com/elixir-grpc/grpc/commit/8aaf3d3a8c4c7b08ac65e9c6f254e0d24da1d048
- github.com/elixir-grpc/grpc/commit/953ab980d8a127e895d3ab9505fc4b9337bb32f7
- github.com/elixir-grpc/grpc/security/advisories/GHSA-xc5v-89vq-hv5m
- osv.dev/vulnerability/EEF-CVE-2026-124278
Vendor advisories and official records. Exploit/PoC links are deliberately left out.