CVE-2026-48597
MediumCVSS 5.9Exploitation Probability (EPSS)
Low risk28th percentile - higher than 28% of all known CVEs
Summary
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.
Risk Assessment
Risk of DoS attack on Elixir application by exhausting the atom table, leading to system crash.
Recommendation
Update the Tesla library to version 1.18.3 or later.
Other vulnerabilities in Tesla
See all- 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.
- CVE-2026-48594High
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.
Original NVD description (English source)
Allocation of Resources Without Limits or Throttling vulnerability in elixir-tesla tesla allows denial of service via atom table exhaustion in Tesla.Adapter.Mint. Tesla.Adapter.Mint.open_conn/2 converts the URL scheme of every outgoing request to a BEAM atom via String.to_atom(uri.scheme) with no allow-list validation. BEAM atoms are never garbage-collected and the atom table is bounded (approximately 1,048,576 entries by default). An attacker who can influence the URL of a Tesla request — either via an application-level URL-forwarding feature (webhook, proxy, importer) or via a Location header returned by a server when Tesla.Middleware.FollowRedirects is in the pipeline — can mint one fresh permanent atom per request by varying the scheme string. After enough requests the atom table fills and the VM crashes, taking down the entire application. This issue affects tesla: from 1.3.0 before 1.18.3.