<?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>Thu, 08 Oct 2026 21:32:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-42786 — WebSocket fragmented message reassembly unbounded in bandit</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-42786</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; mtrudel bandit&lt;/p&gt;
&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in mtrudel bandit allows unauthenticated remote denial of service via memory exhaustion.&lt;/p&gt;
&lt;p&gt;The fragment reassembly path in &amp;#39;Elixir.Bandit.WebSocket.Connection&amp;#39;:handle_frame/3 in lib/bandit/websocket/connection.ex appends every incoming Continuation{fin: false} frame&amp;#39;s payload to a per-connection iolist with no cumulative size cap. The existing max_frame_size option only bounds individual frames; a peer that streams an unbounded number of continuation frames without ever setting fin=1 grows BEAM heap linearly until the OS or a supervisor kills the process.&lt;/p&gt;
&lt;p&gt;Because the accumulation happens before WebSock.handle_in/2 is called, the application has no opportunity to interpose a size check. Phoenix Channels and LiveView both run over WebSock on Bandit, so a stock Phoenix application exposes this surface as soon as it accepts socket connections.&lt;/p&gt;
&lt;p&gt;This issue affects bandit: from 0.5.0 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;Allocation of Resources Without Limits or Throttling vulnerability in mtrudel bandit allows unauthenticated remote denial of service via memory exhaustion.&lt;/p&gt;
&lt;p&gt;The fragment reassembly path in &amp;#39;Elixir.Bandit.WebSocket.Connection&amp;#39;:handle_frame/3 in lib/bandit/websocket/connection.ex appends every incoming Continuation{fin: false} frame&amp;#39;s payload to a per-connection iolist with no cumulative size cap. The existing max_frame_size option only bounds individual frames; a peer that streams an unbounded number of continuation frames without ever setting fin=1 grows BEAM heap linearly until the OS or a supervisor kills the process.&lt;/p&gt;
&lt;p&gt;Because the accumulation happens before WebSock.handle_in/2 is called, the application has no opportunity to interpose a size check. Phoenix Channels and LiveView both run over WebSock on Bandit, so a stock Phoenix application exposes this surface as soon as it accepts socket connections.&lt;/p&gt;
&lt;p&gt;This issue affects bandit: from 0.5.0 before 1.11.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-42786</guid>
    </item>
  </channel>
</rss>
