elixir-tesla up to 1.18.2 add_content_type_param response splitting

Summaryinfo

A vulnerability identified as problematic has been detected in elixir-tesla tesla up to 1.18.2. This impacts the function add_content_type_param. The manipulation leads to response splitting. This vulnerability is traded as CVE-2026-48596. An attack has to be approached locally. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in elixir-tesla tesla up to 1.18.2 and classified as problematic. This issue affects the function add_content_type_param. The manipulation with an unknown input leads to a response splitting vulnerability. Using CWE to declare the problem leads to CWE-113. The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers. Impacted is integrity. The summary by CVE is:

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in elixir-tesla tesla allows HTTP header injection via Tesla.Multipart.add_content_type_param/2. Tesla.Multipart.add_content_type_param/2 appends caller-supplied strings to the multipart content_type_params list without validating for CR (\r) or LF (\n) characters. Tesla.Multipart.headers/1 then joins these params verbatim with "; " to construct the outgoing Content-Type header value. A param containing \r\n splits the header line, allowing arbitrary headers to be injected into the outbound HTTP request. Any application that forwards untrusted input (such as a user-supplied charset or parameter string) into add_content_type_param/2 is affected. This issue affects tesla: from 0.8.0 before 1.18.3.

The weakness was shared by Peter Ullrich and Jonatan Männchen as GHSA-q7jx-v53g-848w. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-48596 since 05/22/2026. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

Upgrading to version 1.18.3 eliminates this vulnerability. Applying the patch 23601edac5d22ba9407b427967b5bdbda201aec2 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Vehicle Software

Vendor

• elixir-tesla

Name

• tesla

Version

• 1.18.0
• 1.18.1
• 1.18.2

License

• open-source

Website

• Product: https://github.com/elixir-tesla/tesla/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion