<?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 05:35:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-39805 — CL.CL HTTP request smuggling via duplicate Content-Length in bandit</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-39805</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; mtrudel bandit&lt;/p&gt;
&lt;p&gt;Inconsistent Interpretation of HTTP Requests vulnerability in mtrudel bandit allows HTTP request smuggling via duplicate Content-Length headers.&lt;/p&gt;
&lt;p&gt;&amp;#39;Elixir.Bandit.Headers&amp;#39;:get_content_length/1 in lib/bandit/headers.ex uses List.keyfind/3, which returns only the first matching header. When a request contains two Content-Length headers with different values, Bandit silently accepts it, uses the first value to read the body, and dispatches the remaining bytes as a second pipelined request on the same keep-alive connection. RFC 9112 §6.3 requires recipients to treat this as an unrecoverable framing error.&lt;/p&gt;
&lt;p&gt;When Bandit sits behind a proxy that picks the last Content-Length value and forwards the request rather than rejecting it, an unauthenticated attacker can smuggle requests past edge WAF rules, path-based ACLs, rate limiting, and audit logging.&lt;/p&gt;
&lt;p&gt;This issue affects bandit: before 1.11.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; mtrudel bandit&lt;/p&gt;
&lt;p&gt;Inconsistent Interpretation of HTTP Requests vulnerability in mtrudel bandit allows HTTP request smuggling via duplicate Content-Length headers.&lt;/p&gt;
&lt;p&gt;&amp;#39;Elixir.Bandit.Headers&amp;#39;:get_content_length/1 in lib/bandit/headers.ex uses List.keyfind/3, which returns only the first matching header. When a request contains two Content-Length headers with different values, Bandit silently accepts it, uses the first value to read the body, and dispatches the remaining bytes as a second pipelined request on the same keep-alive connection. RFC 9112 §6.3 requires recipients to treat this as an unrecoverable framing error.&lt;/p&gt;
&lt;p&gt;When Bandit sits behind a proxy that picks the last Content-Length value and forwards the request rather than rejecting it, an unauthenticated attacker can smuggle requests past edge WAF rules, path-based ACLs, rate limiting, and audit logging.&lt;/p&gt;
&lt;p&gt;This issue affects bandit: before 1.11.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-39805</guid>
    </item>
  </channel>
</rss>
