<?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>Fri, 09 Oct 2026 08:13:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-49756 — Multipart form-data header injection in Req via unescaped name/filename/content_type</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-49756</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wojtekmach req&lt;/p&gt;
&lt;p&gt;Improper Neutralization of CRLF Sequences (&amp;#39;CRLF Injection&amp;#39;) vulnerability in wojtekmach Req allows multipart parameter smuggling via attacker-influenced part metadata.&lt;/p&gt;
&lt;p&gt;Req.Utils.encode_form_part/2 in lib/req/utils.ex builds the per-part headers by interpolating the caller-supplied name, filename, and content_type values directly into the content-disposition and content-type lines with no escaping or CRLF stripping. A value containing &amp;#34;, \r, or \n closes the surrounding quoted value and starts a new header line; an additional \r\n--&amp;lt;boundary&amp;gt; terminates the current part and prepends a smuggled part of the attacker&amp;#39;s choosing.&lt;/p&gt;
&lt;p&gt;This is reachable through every supported way of supplying a part. It is particularly easy when value is a %File.Stream{}, because filename then defaults to Path.basename(stream.path) and POSIX filenames may legitimately contain \r and \n. Any application that forwards user-controlled filenames (or field names / MIME types) through Req.post/2 with form_multipart: lets an attacker inject arbitrary headers into the outgoing multipart body or smuggle additional fields and parts into the request the victim service sends downstream.&lt;/p&gt;
&lt;p&gt;This issue affects req: from 0.5.3 before 0.6.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wojtekmach req&lt;/p&gt;
&lt;p&gt;Improper Neutralization of CRLF Sequences (&amp;#39;CRLF Injection&amp;#39;) vulnerability in wojtekmach Req allows multipart parameter smuggling via attacker-influenced part metadata.&lt;/p&gt;
&lt;p&gt;Req.Utils.encode_form_part/2 in lib/req/utils.ex builds the per-part headers by interpolating the caller-supplied name, filename, and content_type values directly into the content-disposition and content-type lines with no escaping or CRLF stripping. A value containing &amp;#34;, \r, or \n closes the surrounding quoted value and starts a new header line; an additional \r\n--&amp;lt;boundary&amp;gt; terminates the current part and prepends a smuggled part of the attacker&amp;#39;s choosing.&lt;/p&gt;
&lt;p&gt;This is reachable through every supported way of supplying a part. It is particularly easy when value is a %File.Stream{}, because filename then defaults to Path.basename(stream.path) and POSIX filenames may legitimately contain \r and \n. Any application that forwards user-controlled filenames (or field names / MIME types) through Req.post/2 with form_multipart: lets an attacker inject arbitrary headers into the outgoing multipart body or smuggle additional fields and parts into the request the victim service sends downstream.&lt;/p&gt;
&lt;p&gt;This issue affects req: from 0.5.3 before 0.6.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-49756</guid>
    </item>
  </channel>
</rss>
