Deserialization in Elixir-Grpc Grpc
CVE-2026-48853
- CVSS
- Not scored
- Public exploits
- None known
- EPSS
- 0.008 · 56.8th percentile
- Published
- 2026-06-15
Deserialization of Untrusted Data and Allocation of Resources Without Limits or Throttling vulnerabilities in elixir-grpc grpc allow unauthenticated attackers to crash the BEAM node via atom table exhaustion and, when a decoded term flows into a call site that invokes it, achieve remote code execution on the server.
'Elixir.GRPC.Codec.Erlpack':decode/2 (lib/grpc/codec/erlpack.ex) calls :erlang.binary_to_term/1 on the raw gRPC message body without the :safe option, no size bound, and no type guard. Any unauthenticated peer that sends a request with Content-Type: application/grpc+erlpack can send a crafted payload that mints arbitrary new atoms (which are never garbage-collected, exhausting the bounded atom table and crashing the VM) or that encodes a fun term which, if applied anywhere downstream, executes attacker-controlled code inside the server process.
This issue affects grpc: from 0.4.0 before 1.0.0.
Vulnerability class: Insecure Deserialization
Published · last modified .
EPSS exploit prediction
EPSS 0.008, 56.8th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Elixir-Grpc Grpc — versions 0.4.0, 25bcc569fe2cc4478531a6c546c923205fc751c9
Weakness classification (CWE)
References
- github.com/elixir-grpc/grpc/security/advisories/GHSA-grp7-v8xh-rj7h (related, vendor-advisory)
- EEF CNA record for CVE-2026-48853 (related)
- OSV record EEF-CVE-2026-48853 (related)
- Fix commit 272a97a in elixir-grpc/grpc (patch)
- Introducing commit 25bcc56 in elixir-grpc/grpc (related)