Skip to content
Threat Brief

← All advisories

CVE-2026-48595

High 8.2No known exploitationFix available

Authorization header leaks to third-party origin on cross-origin redirect in Tesla.Middleware.FollowRedirects

Record last updated

CVSS score

8.2

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 43% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-178

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
Normalize all header keys to lowercase before passing them to Tesla. Use "authorization" instead of "Authorization" when setting headers via Tesla.put_header/3 or Tesla.Middleware.Headers. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
elixir-teslateslafrom 1.4.0 before 1.18.31.18.3CVE Program
elixir-teslateslafrom 2d937d5813d7cda5cd726f41824985fb655c920f before db963dba67651b9abd1fc420a1d9679cf6efe182db963dba67651b9abd1fc420a1d9679cf6efe182CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references