Answer in brief
CVE-2026-48595 records a High severity (CVSS 8.2) vulnerability in Authorization header leaks to third-party origin on cross-origin redirect in Tesla.Middleware.FollowRedirects. The current sources do not mark it as known exploited. The current feed maps tesla (erlang), elixir-tesla/elixir-tesla/tesla (generic), elixir-tesla/tesla (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps tesla (erlang), elixir-tesla/elixir-tesla/tesla (generic), elixir-tesla/tesla (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:elixir-tesla:tesla:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| teslaerlang | >=0.6.0,<1.18.3 | 1.18.3 |
| elixir-tesla/elixir-tesla/teslageneric | >=2d937d5813d7cda5cd726f41824985fb655c920f <db963dba67651b9abd1fc420a1d9679cf6efe182 | db963dba67651b9abd1fc420a1d9679cf6efe182 |
| elixir-tesla/teslageneric | >=1.4.0 <1.18.3 | 1.18.3 |
Published upstream
Jun 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 10, 2026
Improper Handling of Case Sensitivity vulnerability in elixir-tesla tesla allows credential leakage to a third-party origin on cross-origin redirects. Tesla.Middleware.FollowRedirects strips security-sensitive headers on cross-origin redirects using a case-sensitive string comparison against a lowercase filter list (@filter_headers ["authorization", "host"]). HTTP header names are case-insensitive per RFC 7230, but Tesla preserves header keys verbatim as supplied by the caller without normalizing case. A header set as {"Authorization", "Bearer …"} (the RFC 7235 canonical casing used by virtually all HTTP libraries and documentation) does not match the lowercase filter entry and is forwarded to the redirect destination. An attacker who can control or influence a Location: response seen by the client (via their own endpoint, a redirect-open upstream, or a compromised origin) receives the bearer token or other Authorization material on the cross-origin request. This issue affects tesla: from 1.4.0 before 1.18.3.
Quoted source text, attributed separately from HOL analysis.