Vulnerability EEF-CVE-2026-48595

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
5 months ago
June 02, 2026 at 07:08 PM UTC
Authorization header leaks to third-party origin on cross-origin redirect in Tesla.Middleware.FollowRedirects
1.4.0 - 1.18.2
1.4.0 - 1.18.2

Summary

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

Details

Summary

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.

Workarounds

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.

Configurations

The application must include Tesla.Middleware.FollowRedirects in its Tesla middleware pipeline.

Impacted packages

Timeline

Published
5 months ago
June 02, 2026 at 07:08 PM UTC
Fixed (1.18.3)
5 months ago
June 02, 2026 at 07:05 PM UTC
Last Modified
2 days ago
November 20, 2026 at 06:00 AM UTC