CVE-2026-48598
Last modified
CVE-2026-48598 is a low-severity vulnerability rated 3.7/10 on the CVSS scale. Improper Encoding or Escaping of Output vulnerability in elixir-tesla tesla allows multipart part header injection via unescaped Content-Disposition parameter values. Tesla.Multipart.part_headers_for_disposition/1 interpolates each disposition parameter as #{k}="#{v}" with no validation of CR (\r), LF (\n), or double-quote characters. The values come verbatim from the caller via Tesla.Multipart.add_field/4 (the name parameter), Tesla.Multipart.add_file/3, and Tesla.Multipart.add_file_content/4 (both the filename parameter and other disposition opts). EPSS estimates a 0.34% chance of exploitation in the next 30 days.
Description
Improper Encoding or Escaping of Output vulnerability in elixir-tesla tesla allows multipart part header injection via unescaped Content-Disposition parameter values. Tesla.Multipart.part_headers_for_disposition/1 interpolates each disposition parameter as #{k}="#{v}" with no validation of CR (\r), LF (\n), or double-quote characters. The values come verbatim from the caller via Tesla.Multipart.add_field/4 (the name parameter), Tesla.Multipart.add_file/3, and Tesla.Multipart.add_file_content/4 (both the filename parameter and other disposition opts). A " in the value closes the quoted parameter early; a \r\n ends the Content-Disposition header line and starts a new part header (such as a forged Content-Type), or, after a second \r\n, ends the entire part header block and prepends bytes to the part body. The default-filename path in add_file/3 derives the filename via Path.basename/1, which does not strip CR or LF, so any application forwarding a partially-attacker-controlled file path inherits the same issue. 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-48598.htmlMitigation, Third Party Advisory
- https://osv.dev/vulnerability/EEF-CVE-2026-48598Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-48598?
How severe is CVE-2026-48598?
How do I fix CVE-2026-48598?
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-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-48596Improper Neutralization of CRLF Sequences in HTTP Headers ('…3.7
- CVE-2026-48597Allocation of Resources Without Limits or Throttling vulnera…5.9
- 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
- CVE-2026-48611Improper authentication checks in the OAuth implementation a…9.8
- CVE-2026-48612Improper state verification in the OAuth implementation coul…8
Are you affected by CVE-2026-48598?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
