Quick answers
- Is CVE-2026-48598 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48598 being exploited in the wild.
- How severe is CVE-2026-48598?
- Low severity, with a CVSS score of 2.1, published 2 June 2026.
- Which products and versions are affected?
- elixir-tesla tesla >= 0.8.0, < 1.18.3.
- Is there a fix for CVE-2026-48598?
- A patch was published on 2026-07-10: Fix confirmed in version 1.18.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48598 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-48598?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in `Tesla.Multipart.part_headers_for_disposition/1` due to improper encoding of `Content-Disposition` parameter values. The library interpolates values like filenames and field names directly into headers without escaping double-quotes or CRLF sequences. An attacker providing a crafted filename containing `\r\n` can terminate the current header and inject arbitrary new headers or even prepend data to the part body. This is a form of multipart smuggling that affects applications passing untrusted input to `add_field/4`, `add_file/3`, or `add_file_content/4`. The issue is fixed in version 1.18.3.
Affected products
- elixir-tesla tesla >= 0.8.0, < 1.18.3
Identifiers
- CVE-2026-48598
- GHSA-28jh-g32x-v9v4
Timeline
- 2026-06-02: disclosed: NVD publication date
- 2026-07-10: advisory: GitHub Advisory published
- 2026-07-10: patched: Fix confirmed in version 1.18.3