CVE-2026-48594 Details
Description
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.
A denial-of-service vulnerability has been identified in the Elixir Tesla library, specifically in versions 0.6.0 prior to 1.18.3. The issue arises in the middleware components 'Tesla.Middleware.DecompressResponse' and 'Tesla.Middleware.Compression', which, when included in a Tesla middleware pipeline, decompress HTTP response bodies eagerly and without any size limit. This flaw allows an attacker to send a small, compressed payload that, once decompressed, expands into a massive amount of memory, effectively crashing or freezing the application. The vulnerability exploits the absence of a size cap on decompressed data, particularly with gzip encoding, where a response can be inflated by approximately 1000 times per compression layer, leading to exponential data amplification and memory exhaustion.
The vulnerability has been patched in Tesla version 1.18.3. Users should update to this version. For applications that require the 'Tesla.Middleware.Compression' middleware, it is now mandatory to set the ':max_body_size' option to define a maximum size for decompressed response bodies.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 3, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/elixir-tesla/tesla/security/advisories/GHSA-mc85-72gr-vm9f | CISA-ADP | ExploitVendor Advisory |
| https://cna.erlef.org/cves/CVE-2026-48594.html | EEF | Third Party Advisory |
| https://github.com/elixir-tesla/tesla/commit/340f75b5d191dc747ef7ac6365bd002d1cd55a9d | EEF | Patch |
| https://github.com/elixir-tesla/tesla/commit/5bd90bb5cf0d15e375edc2a66fa322292940fce2 | EEF | |
| https://github.com/elixir-tesla/tesla/security/advisories/GHSA-mc85-72gr-vm9f | EEF | ExploitVendor Advisory |
| https://osv.dev/vulnerability/EEF-CVE-2026-48594 | EEF | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-409 | Improper Handling of Highly Compressed Data (Data Amplification) | EEF |
Affected Products
| Product | Versions |
|---|---|
| elixir-tesla tesla | >= 0.6.0, < 1.18.3 |
CPE
Remediation
| |
Change History
8 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 24, 2026 | CVE Modified | EEF |
| Sep 24, 2026 | CVE Modified | CISA-ADP |
| Aug 17, 2026 | Initial Analysis | [email protected] |
| Jul 22, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | EEF |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 3, 2026 | CVE Modified | CISA-ADP |
| Jun 2, 2026 | New CVE Received | EEF |