CVE-2026-48597: Tesla Tesla Vulnerable To Atom Exhaustion Vulnerability

HIGH
Advisory Identifier: GHSA-h74c-q9j7-mpcm
CWE-770
Published
Advisory Summary

CVE-2026-48597 is a HIGH tesla vulnerable to atom exhaustion vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Tesla libraries in the Hex ecosystem. The issue involves tesla vulnerable to atom exhaustion via untrusted url scheme. Remediation is available by upgrading affected packages to version 1.18.3.

CVE-2026-48597 at a Glance

CVE Identifier CVE-2026-48597
GHSA Identifier GHSA-h74c-q9j7-mpcm
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Tesla
Package Ecosystem Hex
Published Date
Last Updated

How to Fix CVE-2026-48597

To remediate this vulnerability, upgrade all affected Tesla dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

tesla fixed: 1.18.3
Upgrade tesla to 1.18.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for tesla

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-48597, inspect your project dependencies for Tesla:

inspect dependencies for tesla

Analyze the terminal output to locate any version of Tesla in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.18.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Tesla, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary In the Mint adapter for the Tesla HTTP client library, `Tesla.Adapter.Mint.open_conn/2` passes the URL scheme of every outgoing request through `String.to_atom/1` with no allow-list validation. Because BEAM atoms are permanent (never garbage-collected) and the atom table is bounded at roughly 1,048,576 entries, an attacker who can vary the URL scheme across requests can mint one fresh atom per request and eventually exhaust the table, crashing the VM. ### Details **Vulnerable call** (`lib/tesla/adapter/mint.ex`, `open_conn/2`): the scheme field parsed from the request URI is passed directly to `String.to_atom/1` before being forwarded to `Mint.HTTP.connect/4`. Even though `Mint` raises for unrecognised schemes, the atom is already interned by that point. The function's HTTPS-branch guard confirms that no scheme normalisation occurs beforehand. The attack surface has two entry points. First, any application-level URL-forwarding feature (webhook relay, link preview, SSRF-style proxy) where untrusted input reaches `Tesla.get/2` or equivalent. Second, any pipeline that includes `Tesla.Middleware.FollowRedirects`: a server under the attacker's control can return a `Location` header with a novel scheme, triggering the atom creation on the redirect follow. ### PoC 1. Stand up any application that accepts a user-supplied URL and forwards it through `Tesla.Adapter.Mint`. 2. Send requests to the application, each with a distinct, previously unseen URL scheme (e.g. `atk1://`, `atk2://`, ...). 3. Each request interns one new permanent atom; `Mint` rejects the connection but the atom persists. 4. After approximately 1,000,000 requests the BEAM atom table is exhausted and the VM crashes. ### Impact High severity (CVSS v4.0: 8.2). Any application using `tesla` 1.3.0 through 1.18.2 with `Tesla.Adapter.Mint` that allows untrusted input to influence request URLs is vulnerable to remote denial of service. No authentication or special privileges are required beyond access to the application's HTTP endpoint. Fixed in tesla 1.18.3. ### 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 * Introduction commit: https://github.com/elixir-tesla/tesla/commit/ccd0823d4ba37581a37d8f6108f9a81b263237ef * Patch commit: https://github.com/elixir-tesla/tesla/commit/4699c3cb3e2fd6078f99f45f11cf7466aeedbf0e

CVE-2026-48597 Affected Tesla Versions

1 component(s)
Fixed Versions:
1.18.3
Product / Package Ecosystem Affected Versions Fixed Version
tesla
Hex
≥ 1.3.0
< 1.18.3
1.18.3

References

Frequently Asked Questions

What is CVE-2026-48597?
CVE-2026-48597 is a security vulnerability in Tesla involving Tesla vulnerable to atom exhaustion via untrusted URL scheme under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Tesla versions are affected?
Affected versions include releases prior to 1.18.3 across affected packages: tesla.
What version fixes CVE-2026-48597?
Upgrading to 1.18.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is tesla affected?
Yes, tesla is affected in releases prior to 1.18.3. Upgrade your dependency to 1.18.3 or later.
What CWE is associated with CVE-2026-48597?
CVE-2026-48597 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check Hex dependencies for CVE-2026-48597?
Run the dependency tree command: 'inspect dependencies for tesla'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h74c-q9j7-mpcm",
  "modified" : "2026-07-10T00:03:51Z",
  "published" : "2026-07-10T00:03:51Z",
  "aliases" : [ "CVE-2026-48597" ],
  "summary" : "Tesla vulnerable to atom exhaustion via untrusted URL scheme",
  "details" : "### Summary\n\nIn the Mint adapter for the Tesla HTTP client library, `Tesla.Adapter.Mint.open_conn/2` passes the URL scheme of every outgoing request through `String.to_atom/1` with no allow-list validation. Because BEAM atoms are permanent (never garbage-collected) and the atom table is bounded at roughly 1,048,576 entries, an attacker who can vary the URL scheme across requests can mint one fresh atom per request and eventually exhaust the table, crashing the VM.\n\n### Details\n\n**Vulnerable call** (`lib/tesla/adapter/mint.ex`, `open_conn/2`): the scheme field parsed from the request URI is passed directly to `String.to_atom/1` before being forwarded to `Mint.HTTP.connect/4`. Even though `Mint` raises for unrecognised schemes, the atom is already interned by that point. The function's HTTPS-branch guard confirms that no scheme normalisation occurs beforehand.\n\nThe attack surface has two entry points. First, any application-level URL-forwarding feature (webhook relay, link preview, SSRF-style proxy) where untrusted input reaches `Tesla.get/2` or equivalent. Second, any pipeline that includes `Tesla.Middleware.FollowRedirects`: a server under the attacker's control can return a `Location` header with a novel scheme, triggering the atom creation on the redirect follow.\n\n### PoC\n\n1. Stand up any application that accepts a user-supplied URL and forwards it through `Tesla.Adapter.Mint`.\n2. Send requests to the application, each with a distinct, previously unseen URL scheme (e.g. `atk1://`, `atk2://`, ...).\n3. Each request interns one new permanent atom; `Mint` rejects the connection but the atom persists.\n4. After approximately 1,000,000 requests the BEAM atom table is exhausted and the VM crashes.\n\n### Impact\n\nHigh severity (CVSS v4.0: 8.2). Any application using `tesla` 1.3.0 through 1.18.2 with `Tesla.Adapter.Mint` that allows untrusted input to influence request URLs is vulnerable to remote denial of service. No authentication or special privileges are required beyond access to the application's HTTP endpoint. Fixed in tesla 1.18.3.\n\n### Configurations\n\nThe 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.\n\n### References\n\n* Introduction commit: https://github.com/elixir-tesla/tesla/commit/ccd0823d4ba37581a37d8f6108f9a81b263237ef\n* Patch commit: https://github.com/elixir-tesla/tesla/commit/4699c3cb3e2fd6078f99f45f11cf7466aeedbf0e",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Hex",
      "name" : "tesla"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.3.0"
      }, {
        "fixed" : "1.18.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/elixir-tesla/tesla/security/advisories/GHSA-h74c-q9j7-mpcm"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48597"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/elixir-tesla/tesla/commit/4699c3cb3e2fd6078f99f45f11cf7466aeedbf0e"
  }, {
    "type" : "WEB",
    "url" : "https://cna.erlef.org/cves/CVE-2026-48597.html"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/elixir-tesla/tesla"
  }, {
    "type" : "WEB",
    "url" : "https://osv.dev/vulnerability/EEF-CVE-2026-48597"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-10T00:03:51Z",
    "nvd_published_at" : "2026-06-02T20:16:38Z"
  }
}