CVE-2026-48594
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk38th percentile - higher than 38% of all known CVEs
Summary
Vulnerability in the Tesla library for Elixir (versions 0.6.0 up to before 1.18.3) due to improper handling of highly compressed data (decompression bomb). HTTP responses are decompressed without size limits, and multiple compression layers can lead to exponential data expansion, causing memory exhaustion and denial of service.
Risk Assessment
Risk of DoS attack by sending HTTP responses with multiple compression layers, potentially exhausting BEAM memory and crashing the process.
Recommendation
Update the Tesla library to version 1.18.3 or later and limit the size of decompressed data.
Other vulnerabilities in Tesla
See all- CVE-2026-48597Medium
Resource exhaustion vulnerability in the Tesla library (Elixir) before version 1.18.3. Tesla.Adapter.Mint.open_conn/2 converts the URL scheme of every request to a BEAM atom without validation, potentially filling the atom table and crashing the VM. An attacker can influence the request URL via redirect features or webhooks.
- CVE-2026-48596Low
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in elixir-tesla tesla allows HTTP header injection via Tesla.Multipart.add_content_type_param/2. Tesla.Multipart.add_content_type_param/2 appends caller-supplied strings to the multipart content_type_params list without validating for CR (\r) or LF (\n) characters. Tesla.Multipart.headers/1 then joins these params verbatim with "; " to construct the outgoing Content-Type header value. A param containing \r\n splits the header line, allowing arbitrary headers to be injected into the outbound HTTP request.
- CVE-2026-48595Medium
Tesla library (Elixir) versions from 1.4.0 before 1.18.3 improperly handle case sensitivity in HTTP headers during cross-origin redirects. The Authorization header in canonical form (e.g., "Authorization") is not filtered, leading to credential leakage to a third-party origin.
Original NVD description (English source)
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.