Skip to main content
← All vulnerabilities
CVE-2026-48594EEF-CVE-2026-48594GHSA-MC85-72GR-VM9F

Decompression bomb in Tesla.Middleware.DecompressResponse and Tesla.Middleware.Compression

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 1.18.3
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in elixir-tesla tesla allows a denial of service via decompression bomb in HTTP response bodies. When Tesla.Middleware.DecompressResponse or Tesla.Middleware.Compression is included in a Tesla middleware pipeline, HTTP response bodies are decompressed eagerly with no size limit. The decompress_body/2 function in lib/tesla/middleware/compression.ex passes the entire response body to :zlib.gunzip/1 or :zlib.unzip/1 without any cap on the output size. Additionally, compression_algorithms/1 splits the content-encoding header on commas and decompress_body/2 recurses once per token, applying a decompression pass on each iteration. A server advertising content-encoding: gzip, gzip, gzip, gzip causes four recursive decompression passes, yielding exponential amplification: each gzip layer can expand its input roughly 1000x, so a payload of a few hundred bytes on the wire inflates to gigabytes of BEAM heap, exhausting memory and crashing or freezing the calling process. This issue affects tesla: from 0.6.0 before 1.18.3.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • tesla

    From 0.6.0 · fixed in 1.18.3

  • elixir-tesla/tesla

    From 5bd90bb5cf0d15e375edc2a66fa322292940fce2 · fixed in 340f75b5d191dc747ef7ac6365bd002d1cd55a9d

  • teslaHex

    From 0.6.0 · fixed in 1.18.3

References 5

GitHub · elixir-tesla/tesla

cna.erlef.org

osv.dev