CVE-2026-48854: Grpc GRPC Erlang Package Has Unbounded Vulnerability
HIGHCVE-2026-48854 is a HIGH grpc erlang package has unbounded vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Grpc libraries in the Hex ecosystem. The issue involves grpc erlang package has unbounded request body accumulation in `read_full_body/3`. Remediation is available by upgrading affected packages to version 1.0.0.
CVE-2026-48854 at a Glance
How to Fix CVE-2026-48854
To remediate this vulnerability, upgrade all affected Grpc dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade grpc to 1.0.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for grpc
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-48854, inspect your project dependencies for Grpc:
inspect dependencies for grpc
Analyze the terminal output to locate any version of Grpc in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Grpc, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-48854 Affected Grpc Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
grpc
|
Hex |
≥ 0.3.1
< 1.0.0
|
1.0.0
|
References
Frequently Asked Questions
What is CVE-2026-48854?
Which Grpc versions are affected?
What version fixes CVE-2026-48854?
Is grpc affected?
What CWE is associated with CVE-2026-48854?
How can I check Hex dependencies for CVE-2026-48854?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-q8gf-9rvj-gmgj",
"modified" : "2026-08-25T18:12:05Z",
"published" : "2026-08-25T18:12:05Z",
"aliases" : [ "CVE-2026-48854" ],
"summary" : "gRPC Erlang package has unbounded request body accumulation in `read_full_body/3`",
"details" : "### Summary\n\n`'Elixir.GRPC.Server.Adapters.Cowboy.Handler':read_full_body/3` accumulates every received chunk into a single growing binary with no size cap. When the client omits the `grpc-timeout` header, the read timeout resolves to `:infinity`, allowing a slow-trickle attacker to hold the connection open indefinitely while memory grows. A single unauthenticated connection is sufficient to exhaust BEAM memory and crash the node.\n\n### Details\n\nThe read loop in `lib/grpc/server/adapters/cowboy/handler.ex` calls `:cowboy_req.read_body/2` in a recursive loop, concatenating each chunk: `body <> data`. There is no running-total check and no configurable maximum body size. As the loop drains the receive buffer, cowboy issues fresh HTTP/2 `WINDOW_UPDATE` frames, so the client can keep pushing data indefinitely.\n\nThe `grpc-timeout` header is attacker-supplied and optional. When absent, `timeout_left_opt(nil)` returns `:infinity`, so the per-chunk read also has no deadline. The two missing controls compound: a fast client can blast multi-gigabyte payloads directly into memory; a slow client can trickle data forever.\n\n### PoC\n\n1. Start any `grpc` server exposing a unary RPC (no special configuration required).\n2. Open an HTTP/2 connection and send a POST to any unary RPC path with `Content-Type: application/grpc+proto` — omit the `grpc-timeout` header.\n3. Stream a large body (e.g. 1 GiB) in chunks without sending the final `END_STREAM` flag immediately.\n4. Observe BEAM memory growing proportionally to uploaded data with no server-side cap.\n\n### Impact\n\nAffects `grpc` ≥ 0.3.1. No authentication, no special configuration, and no specific RPC method required, the unbounded read is on the default unary ingress path.\n\n### References\n\n* Introduction commit: https://github.com/elixir-grpc/grpc/commit/d1abe70a6cad6dac4a3f8235d883d7c896989560\n* Patch commit: https://github.com/elixir-grpc/grpc/commit/49e18c3ec6bb9afe2f712caad3dbab5c56a68a00",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Hex",
"name" : "grpc"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.3.1"
}, {
"fixed" : "1.0.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/elixir-grpc/grpc/security/advisories/GHSA-q8gf-9rvj-gmgj"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48854"
}, {
"type" : "WEB",
"url" : "https://github.com/elixir-grpc/grpc/pull/542"
}, {
"type" : "WEB",
"url" : "https://github.com/elixir-grpc/grpc/commit/49e18c3ec6bb9afe2f712caad3dbab5c56a68a00"
}, {
"type" : "WEB",
"url" : "https://cna.erlef.org/cves/CVE-2026-48854.html"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/elixir-grpc/grpc"
}, {
"type" : "WEB",
"url" : "https://github.com/elixir-grpc/grpc/releases/tag/v1.0.0"
}, {
"type" : "WEB",
"url" : "https://osv.dev/vulnerability/EEF-CVE-2026-48854"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-770" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-25T18:12:05Z",
"nvd_published_at" : "2026-06-15T23:16:45Z"
}
}