Skip to main content
VulnerabilityPublished Updated

CVE-2026-48595: tesla · Improper Handling of Case Sensitivity

Affects teslaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 1.18.3 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.18.3, db963dba67651b9abd1fc420a1d9679cf6efe182
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade tesla to 1.18.3; tesla to db963dba67651b9abd1fc420a1d9679cf6efe182.

Affected software

ProductAffectedFixed in
elixir-teslateslaAffected
  • >=1.4.0 <1.18.3
Fixed in
  • 1.18.3
elixir-teslateslaAffected
  • ≥ 2d937d5813d7cda5cd726f41824985fb655c920f, < db963dba67651b9abd1fc420a1d9679cf6efe182
Fixed in
  • db963dba67651b9abd1fc420a1d9679cf6efe182
Hexteslapkg:hex/teslaOther threatsAffected
  • =1.4.0
Fixed in–
Hexteslapkg:hex/teslaOther threatsAffected
  • >=1.4.0 <1.18.3
Fixed in
  • 1.18.3

CPE configurations (1)

  • cpe:2.3:a:elixir-tesla:tesla:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should avoid using vulnerable versions or implement custom middleware to normalize header casing before redirects to ensure sensitive headers are properly stripped.

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.

References

Community reviews

Loading reviews…