<?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>Wed, 07 Oct 2026 05:45:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-39804 — WebSocket permessage-deflate inflate has no output-size cap in bandit</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-39804</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 when WebSocket permessage-deflate compression is enabled.&lt;/p&gt;
&lt;p&gt;&amp;#39;Elixir.Bandit.WebSocket.PerMessageDeflate&amp;#39;:inflate/2 in lib/bandit/websocket/permessage_deflate.ex calls :zlib.inflate/2 with no output-size cap, then materializes the entire decompressed payload as a single binary via IO.iodata_to_binary/1. The websocket_options.max_frame_size option only bounds the on-the-wire (compressed) frame size, not the decompressed output. A high-ratio compressed frame (e.g. uniform data at ~1024:1 ratio) can stay well under any wire-size limit while forcing GiB-scale heap allocations in the connection process before any application code runs.&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker who can open a WebSocket connection can send a single such frame to exhaust the BEAM node&amp;#39;s memory and trigger an OOM kill.&lt;/p&gt;
&lt;p&gt;This vulnerability requires both Bandit&amp;#39;s server-level websocket_options.compress and the per-upgrade compress: true option passed to WebSockAdapter.upgrade/4 to be enabled. Stock Phoenix and LiveView applications are not affected as they default to compress: false.&lt;/p&gt;
&lt;p&gt;This issue affects bandit: from 0.5.9 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 when WebSocket permessage-deflate compression is enabled.&lt;/p&gt;
&lt;p&gt;&amp;#39;Elixir.Bandit.WebSocket.PerMessageDeflate&amp;#39;:inflate/2 in lib/bandit/websocket/permessage_deflate.ex calls :zlib.inflate/2 with no output-size cap, then materializes the entire decompressed payload as a single binary via IO.iodata_to_binary/1. The websocket_options.max_frame_size option only bounds the on-the-wire (compressed) frame size, not the decompressed output. A high-ratio compressed frame (e.g. uniform data at ~1024:1 ratio) can stay well under any wire-size limit while forcing GiB-scale heap allocations in the connection process before any application code runs.&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker who can open a WebSocket connection can send a single such frame to exhaust the BEAM node&amp;#39;s memory and trigger an OOM kill.&lt;/p&gt;
&lt;p&gt;This vulnerability requires both Bandit&amp;#39;s server-level websocket_options.compress and the per-upgrade compress: true option passed to WebSockAdapter.upgrade/4 to be enabled. Stock Phoenix and LiveView applications are not affected as they default to compress: false.&lt;/p&gt;
&lt;p&gt;This issue affects bandit: from 0.5.9 before 1.11.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-39804</guid>
    </item>
  </channel>
</rss>
