PT-2026-49535 · Elixir Grpc+2 · Grpc
Paulo Valente
+1
·
Published
2026-06-09
·
Updated
2026-06-16
·
CVE-2026-53430
CVSS v4.0
8.7
High
| Vector | AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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 |
Name of the Vulnerable Software and Affected Versions
elixir-grpc versions 0.4.0 through 0.9.x
Description
Improper handling of highly compressed data in the
GRPC.Compressor.Gzip and GRPC.Message modules allows a denial of service via a gzip decompression bomb. The function decompress/1 in Elixir.GRPC.Compressor.Gzip calls :zlib.gunzip/1 on attacker-controlled bytes without a decompressed-size limit, ratio check, or incremental decoding. This occurs automatically when an incoming gRPC frame contains the grpc-encoding: gzip header. Since :zlib.gunzip/1 allocates the entire decompressed result as a single binary, a small, highly compressible payload can expand to multiple gigabytes, exhausting the BEAM node's heap and triggering an out-of-memory kill. The max receive message length limit is ineffective as it is only enforced after decompression. This can be exploited by an unauthenticated remote peer using the from data/2 function in Elixir.GRPC.Message.Recommendations
Update to version 1.0.0 or later.
Exploit
Fix
DoS
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Grpc