<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T20:30:01.667651+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/brew-mailcatcher-cve-2026-61666</id>
    <title>BREW-mailcatcher-CVE-2026-61666 — websocket-driver-ruby: Denial of service via malformed Host header</title>
    <updated>2026-09-28T20:30:01.760541+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: mailcatcher</p>
<p>### Impact</p>
<p>If this library is used to implement a WebSocket server on top of a TCP server, by using the `WebSocket::Driver.server()` method, then a client can cause the server to crash by sending a `Host` header that is not a valid `host[:port]` string. When this happens, a `URI::InvalidURIError` exception is raised which is not caught, and this can cause the server process to crash if the application does not catch the error from the `parse()` method itself.</p>
<p>### Patches</p>
<p>The issue has been patched in version 0.8.2 by making the request parser catch `URI::InvalidURIError` and enter an error state if the `Host` header is malformed. This means the request is considered invalid and should not establish a WebSocket connection.</p>
<p>### Workarounds</p>
<p>No known workarounds exist.</p>
<p>### Acknowledgements</p>
<p>This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-mailcatcher-cve-2026-61666"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-61666</id>
    <title>fkie_cve-2026-61666</title>
    <updated>2026-09-28T20:30:01.760731+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.2, WebSocket::Driver.server() passes a malformed Host header to URI.parse in lib/websocket/http/request.rb without catching URI::InvalidURIError, allowing a remote client to crash a TCP-backed WebSocket server when the application does not catch the error from parse(). This issue is fixed in version 0.8.2.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-61666"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-2x63-gw47-w4mm</id>
    <title>GHSA-2x63-gw47-w4mm — websocket-driver-ruby: Denial of service via malformed Host header</title>
    <updated>2026-09-28T20:30:01.760787+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> RubyGems: websocket-driver</p>
<p>### Impact</p>
<p>If this library is used to implement a WebSocket server on top of a TCP server, by using the `WebSocket::Driver.server()` method, then a client can cause the server to crash by sending a `Host` header that is not a valid `host[:port]` string. When this happens, a `URI::InvalidURIError` exception is raised which is not caught, and this can cause the server process to crash if the application does not catch the error from the `parse()` method itself.</p>
<p>### Patches</p>
<p>The issue has been patched in version 0.8.2 by making the request parser catch `URI::InvalidURIError` and enter an error state if the `Host` header is malformed. This means the request is considered invalid and should not establish a WebSocket connection.</p>
<p>### Workarounds</p>
<p>No known workarounds exist.</p>
<p>### Acknowledgements</p>
<p>This issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-2x63-gw47-w4mm"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/oesa-2026-3218</id>
    <title>OESA-2026-3218 — rubygem-websocket-driver security update</title>
    <updated>2026-09-28T20:30:01.760847+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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.

Security Fix(es):</p>
<p>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)</p>
<p>### Impact</p>
<p>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;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.</p>
<p>### Patc…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/oesa-2026-3218"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-61666</id>
    <title>UBUNTU-CVE-2026-61666</title>
    <updated>2026-09-28T20:30:01.760948+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.2, WebSocket::Driver.server() passes a malformed Host header to URI.parse in lib/websocket/http/request.rb without catching URI::InvalidURIError, allowing a remote client to crash a TCP-backed WebSocket server when the application does not catch the error from parse(). This issue is fixed in version 0.8.2.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-61666"/>
  </entry>
</feed>
