cve.bz

CVE-2026-53430 grpc gzip decompression bomb in GRPC.Compressor.Gzip.decompress/1

8.7 highEPSS 0.4%Fix available

High (8.7) in elixir-grpc grpc. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in grpc 1.0.0.

On this page
Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in elixir-grpc grpc (GRPC.Compressor.Gzip, GRPC.Message modules) allows a denial of service via a gzip decompression bomb. This vulnerability is associated with program files lib/grpc/compressor/gzip.ex, lib/grpc/message.ex and program routines GRPC.Compressor.Gzip.decompress/1, GRPC.Message.from_data/2. GRPC.Compressor.Gzip.decompress/1 calls :zlib.gunzip/1 directly on attacker-controlled bytes with no decompressed-size limit, ratio check, or incremental decoding. Because this module is the registered gzip GRPC.Compressor implementation, it is invoked automatically whenever an incoming gRPC frame carries the grpc-encoding: gzip header. :zlib.gunzip/1 allocates the entire decompressed result as a single binary, so a small highly compressible payload (for example a few kilobytes of zeros, which gzip compresses at roughly 1000:1) expands to multiple gigabytes inside a single call. The max_receive_message_length limit is enforced only against the already-decompressed message, so it provides no protection. An unauthenticated remote peer can send a single crafted frame to exhaust the BEAM node's heap and trigger an out-of-memory kill. This issue affects grpc: from 0.4.0 before 1.0.0; grpc_core: from 1.0.0-alfa before 1.0.0.

Severity

CVSS 4.0

8.7 high
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
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-06-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • grpc (Hex): fixed in 1.0.0
  • grpc_core (Hex): fixed in 1.0.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-53430 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53430?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53430?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53430 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
elixir-grpc grpcfrom 0.4.0 before 1.0.0
elixir-grpc grpcfrom 1.0.0-alfa before 1.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-53430Hexgrpc>=0.4.0 <1.0.01.0.0
EEF-CVE-2026-53430Hexgrpc_core>=1.0.0-alfa <1.0.01.0.0
EEF-CVE-2026-53430v0.11.2, v0.8.1, v0.8.0, v0.7.0, v0.6.0 and 4 moreno fix published
GHSA-6ccx-9c9f-327wHexgrpc>=0.4.0 <1.0.01.0.0

References

Check your stackJSON