CVE-2026-48594: tesla · Data Amplification
Affects teslaSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 1.18.3 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.18.3, 340f75b5d191dc747ef7ac6365bd002d1cd55a9d
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade tesla to 1.18.3; tesla to 340f75b5d191dc747ef7ac6365bd002d1cd55a9d.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| elixir-teslatesla | Affected
| Fixed in
|
| elixir-teslatesla | Affected
| Fixed in
|
Hexteslapkg:hex/teslaOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:elixir-tesla:tesla:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, avoid using Tesla.Middleware.DecompressResponse or Tesla.Middleware.Compression with untrusted or potentially malicious HTTP responses. Implement application-level limits on decompressed response size if possible to mitigate memory exhaustion.
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.
References
- github.com/elixir-tesla/tesla/security/advisories/GHSA-mc85-72gr-vm9f (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-48594.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-48594 (opens in a new tab)
- github.com/elixir-tesla/tesla/commit/340f75b5d191dc747ef7ac6365bd002d1cd55a9d (opens in a new tab)
- github.com/elixir-tesla/tesla/commit/5bd90bb5cf0d15e375edc2a66fa322292940fce2 (opens in a new tab)