CVE-2026-48596
Last modified
CVE-2026-48596 is a low-severity vulnerability rated 3.7/10 on the CVSS scale. 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. EPSS estimates a 0.35% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Elixir-Tesla | Tesla | >= 0.8.0, < 1.18.3 |
References
- https://cna.erlef.org/cves/CVE-2026-48596.htmlThird Party Advisory
- https://github.com/elixir-tesla/tesla/security/advisories/GHSA-q7jx-v53g-848wExploit, Vendor Advisory
- https://osv.dev/vulnerability/EEF-CVE-2026-48596Third Party Advisory
- https://github.com/elixir-tesla/tesla/security/advisories/GHSA-q7jx-v53g-848wExploit, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-48596?
How severe is CVE-2026-48596?
How do I fix CVE-2026-48596?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-48590XML Injection vulnerability in joshnuss xml_builder (XmlBuil…2.1
- CVE-2026-48591Improper Neutralization of Script in Attributes in a Web Pag…4.8
- CVE-2026-48592Missing Authorization vulnerability in oban-bg oban_web ('El…5.3
- CVE-2026-48593Uncontrolled Resource Consumption vulnerability in oban-bg o…5.9
- CVE-2026-48594Improper Handling of Highly Compressed Data (Data Amplificat…7.5
- CVE-2026-48595Improper Handling of Case Sensitivity vulnerability in elixi…5.9
- CVE-2026-48597Allocation of Resources Without Limits or Throttling vulnera…5.9
- CVE-2026-48598Improper Encoding or Escaping of Output vulnerability in eli…3.7
- CVE-2026-48599Authorization Bypass Through User-Controlled Key vulnerabili…7.6
- CVE-2026-4860A security flaw has been discovered in 648540858 wvp-GB28181…7.3
- CVE-2026-4861A weakness has been identified in Wavlink WL-NU516U1 260227.…8.8
- CVE-2026-48610Under certain network configurations, a malicious actor with…8.1
Are you affected by CVE-2026-48596?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
