<?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>Sun, 04 Oct 2026 16:24:08 +0000</lastBuildDate>
    <item>
      <title>BREW-mailcatcher-CVE-2026-54463 — websocket-driver: Memory exhaustion via abuse of protocol length headers</title>
      <link>https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2026-54463</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: mailcatcher&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values `0x80` or above, a server or client can make the other peer parse these bytes into an ever-growing integer. Since Ruby integers are arbitrary precision, this can be used to make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been patched in version 0.8.1. All users should upgrade to this version.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;No known workarounds exist.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: mailcatcher&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values `0x80` or above, a server or client can make the other peer parse these bytes into an ever-growing integer. Since Ruby integers are arbitrary precision, this can be used to make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been patched in version 0.8.1. All users should upgrade to this version.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;No known workarounds exist.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2026-54463</guid>
    </item>
    <item>
      <title>EUVD-2026-338947</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338947</link>
      <description>EUVD-2026-338947</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338947</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54463</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54463</link>
      <description>&lt;p&gt;websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54463</guid>
    </item>
    <item>
      <title>GHSA-ghhp-3qvg-889p — websocket-driver: Memory exhaustion via abuse of protocol length headers</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ghhp-3qvg-889p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: websocket-driver&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values `0x80` or above, a server or client can make the other peer parse these bytes into an ever-growing integer. Since Ruby integers are arbitrary precision, this can be used to make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been patched in version 0.8.1. All users should upgrade to this version.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;No known workarounds exist.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: websocket-driver&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values `0x80` or above, a server or client can make the other peer parse these bytes into an ever-growing integer. Since Ruby integers are arbitrary precision, this can be used to make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been patched in version 0.8.1. All users should upgrade to this version.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;No known workarounds exist.&lt;/p&gt;
&lt;p&gt;### Acknowledgements&lt;/p&gt;
&lt;p&gt;This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ghhp-3qvg-889p</guid>
    </item>
    <item>
      <title>OESA-2026-3218 — rubygem-websocket-driver security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3218</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: rubygem-websocket-driver, openEuler:22.03-LTS-SP4: rubygem-websocket-driver, openEuler:24.03-LTS-SP1: rubygem-websocket-driver, openEuler:24.03-LTS-SP3: rubygem-websocket-driver, openEuler:24.03-LTS-SP4: rubygem-websocket-driver&lt;/p&gt;
&lt;p&gt;This module provides a complete implementation of the WebSocket protocols that can be hooked up to any TCP library. It aims to simplify things by decoupling the protocol details from the I/O layer, such that users only need to implement code to stream data in and out of it without needing to know anything about how the protocol actually works. Think of it as a complete WebSocket system with pluggable I/O.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.(CVE-2026-54463)&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;If this library is used in tandem with the `permessage-deflate` extension, a
WebSocket server or client can be made to accept messages that are larger than
the configured maximum message size. This is because this limit is checked
against the message frames&amp;amp;apos; length headers, which give the size of the
compressed data, not the size after decompression. This can lead to applications
accepting larger messages than expected and exceeding their intended resource
usage.&lt;/p&gt;
&lt;p&gt;### Patc…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: rubygem-websocket-driver, openEuler:22.03-LTS-SP4: rubygem-websocket-driver, openEuler:24.03-LTS-SP1: rubygem-websocket-driver, openEuler:24.03-LTS-SP3: rubygem-websocket-driver, openEuler:24.03-LTS-SP4: rubygem-websocket-driver&lt;/p&gt;
&lt;p&gt;This module provides a complete implementation of the WebSocket protocols that can be hooked up to any TCP library. It aims to simplify things by decoupling the protocol details from the I/O layer, such that users only need to implement code to stream data in and out of it without needing to know anything about how the protocol actually works. Think of it as a complete WebSocket system with pluggable I/O.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.(CVE-2026-54463)&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;If this library is used in tandem with the `permessage-deflate` extension, a
WebSocket server or client can be made to accept messages that are larger than
the configured maximum message size. This is because this limit is checked
against the message frames&amp;amp;apos; length headers, which give the size of the
compressed data, not the size after decompression. This can lead to applications
accepting larger messages than expected and exceeding their intended resource
usage.&lt;/p&gt;
&lt;p&gt;### Patc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3218</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-54463</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54463</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-websocket-driver, Ubuntu:18.04:LTS: ruby-websocket-driver, Ubuntu:20.04:LTS: ruby-websocket-driver, Ubuntu:22.04:LTS: ruby-websocket-driver, Ubuntu:24.04:LTS: ruby-websocket-driver, Ubuntu:26.04:LTS: ruby-websocket-driver&lt;/p&gt;
&lt;p&gt;websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-websocket-driver, Ubuntu:18.04:LTS: ruby-websocket-driver, Ubuntu:20.04:LTS: ruby-websocket-driver, Ubuntu:22.04:LTS: ruby-websocket-driver, Ubuntu:24.04:LTS: ruby-websocket-driver, Ubuntu:26.04:LTS: ruby-websocket-driver&lt;/p&gt;
&lt;p&gt;websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54463</guid>
    </item>
  </channel>
</rss>
