CVE-2026-48595 Details
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.
A vulnerability in the Elixir Tesla library, specifically in versions 1.4.0 prior to 1.18.3, has been identified. The issue arises in the FollowRedirects middleware, which improperly handles the case sensitivity of HTTP headers. This flaw allows for the leakage of authorization credentials to third-party origins during cross-origin redirects. The middleware is supposed to strip sensitive headers like Authorization and Host when following redirects to different domains. However, it uses a case-sensitive comparison against a lowercase filter list, failing to recognize headers set with their canonical casing as defined by the RFC standards. As a result, headers such as 'Authorization' are not filtered out and can be forwarded to the redirect destination, potentially exposing bearer tokens or other sensitive information. An attacker who can influence the Location response seen by the client can exploit this vulnerability, leading to unauthorized access to the leaked credentials.
Update to Tesla version 1.18.3 or later. If an immediate upgrade is not possible, normalize all header keys to lowercase before sending them, using 'authorization' instead of 'Authorization'.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 3, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/elixir-tesla/tesla/security/advisories/GHSA-9m9w-gxf7-rh8m | CISA-ADP | ExploitVendor Advisory |
| https://cna.erlef.org/cves/CVE-2026-48595.html | EEF | Third Party Advisory |
| https://github.com/elixir-tesla/tesla/commit/2d937d5813d7cda5cd726f41824985fb655c920f | EEF | |
| https://github.com/elixir-tesla/tesla/commit/db963dba67651b9abd1fc420a1d9679cf6efe182 | EEF | Patch |
| https://github.com/elixir-tesla/tesla/security/advisories/GHSA-9m9w-gxf7-rh8m | EEF | ExploitVendor Advisory |
| https://osv.dev/vulnerability/EEF-CVE-2026-48595 | EEF | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-178 | Improper Handling of Case Sensitivity | EEF |
Affected Products
| Product | Versions |
|---|---|
| elixir-tesla tesla | >= 1.4.0, < 1.18.3 |
CPE
Remediation
| |
Change History
8 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 24, 2026 | CVE Modified | EEF |
| Sep 24, 2026 | CVE Modified | CISA-ADP |
| Aug 17, 2026 | Initial Analysis | [email protected] |
| Jul 22, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | EEF |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 3, 2026 | CVE Modified | CISA-ADP |
| Jun 2, 2026 | New CVE Received | EEF |