<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 04:22:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48598 — CRLF injection in Tesla.Multipart disposition parameters allows multipart part header injection</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-48598</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; elixir-tesla tesla&lt;/p&gt;
&lt;p&gt;Improper Encoding or Escaping of Output vulnerability in elixir-tesla tesla allows multipart part header injection via unescaped Content-Disposition parameter values.&lt;/p&gt;
&lt;p&gt;Tesla.Multipart.part_headers_for_disposition/1 interpolates each disposition parameter as #{k}=&amp;#34;#{v}&amp;#34; 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 &amp;#34; 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.&lt;/p&gt;
&lt;p&gt;This issue affects tesla: from 0.8.0 before 1.18.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; elixir-tesla tesla&lt;/p&gt;
&lt;p&gt;Improper Encoding or Escaping of Output vulnerability in elixir-tesla tesla allows multipart part header injection via unescaped Content-Disposition parameter values.&lt;/p&gt;
&lt;p&gt;Tesla.Multipart.part_headers_for_disposition/1 interpolates each disposition parameter as #{k}=&amp;#34;#{v}&amp;#34; 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 &amp;#34; 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.&lt;/p&gt;
&lt;p&gt;This issue affects tesla: from 0.8.0 before 1.18.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-48598</guid>
    </item>
  </channel>
</rss>
