Vulnerability description

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.

Affected

pkg:hex/tesla

Status Type Version Changes / Fixed in
affected semver 1.3.0 < 1.18.3

pkg:github/elixir-tesla/tesla

Module Source File Routine
Tesla.Adapter.Mint lib/tesla/adapter/mint.ex Tesla.Adapter.Mint.open_conn/2
Status Type Version Changes / Fixed in
affected git ccd0823d4b < 4699c3cb3e

Configurations

The application must use Tesla.Adapter.Mint and either expose a feature that forwards attacker-controlled URLs to Tesla, or include Tesla.Middleware.FollowRedirects in the middleware pipeline.

References

Credits

  • Finder: Peter Ullrich
  • Remediation developer: Yordis Prieto
  • Analyst: Jonatan Männchen

CVE record as JSON:  GET /cves/CVE-2026-48597.json
OSV record as JSON:  GET /osv/EEF-CVE-2026-48597.json