Vulnerability EEF-CVE-2026-48594

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
5 months ago
June 02, 2026 at 07:08 PM UTC
Decompression bomb in Tesla.Middleware.DecompressResponse and Tesla.Middleware.Compression
0.6.0 - 1.18.2
0.6.0 - 1.18.2

Summary

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

Details

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.

Configurations

The application must include Tesla.Middleware.DecompressResponse or Tesla.Middleware.Compression in its Tesla middleware pipeline.

Impacted packages

Timeline

Published
5 months ago
June 02, 2026 at 07:08 PM UTC
Fixed (1.18.3)
5 months ago
June 02, 2026 at 07:05 PM UTC
Last Modified
2 days ago
November 20, 2026 at 06:00 AM UTC