<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T03:56:37.871501+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bdu:2024-10889</id>
    <title>bdu:2024-10889</title>
    <updated>2026-10-05T03:56:38.153760+00:00</updated>
    <content>bdu:2024-10889</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2024-10889"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-icloudpd-cve-2024-49768</id>
    <title>BREW-icloudpd-CVE-2024-49768 — Waitress has request processing race condition in HTTP pipelining with invalid first request</title>
    <updated>2026-10-05T03:56:38.153809+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: icloudpd</p>
<p>### Impact</p>
<p>A remote client may send a request that is exactly `recv_bytes` (defaults to 8192) long, followed by a secondary request using HTTP pipelining.</p>
<p>When request lookahead is disabled (default) we won't read any more requests, and when the first request fails due to a parsing error, we simply close the connection.</p>
<p>However when request lookahead is enabled, it is possible to process and receive the first request, start sending the error message back to the client while we read the next request and queue it. This will allow the secondary request to be serviced by the worker thread while the connection should be closed.</p>
<p>### Patches</p>
<p>Waitress 3.0.1 fixes the race condition.</p>
<p>### Workarounds</p>
<p>Disable  `channel_request_lookahead`, this is set to `0` by default disabling this feature. For this vulnerability this value is required to be changed from the default.</p>
<p>### For more information</p>
<p>If you have any questions or comments about this advisory:
* Open an issue in https://github.com/Pylons/waitress/issues (if not sensitive or security related)
* email the Pylons Security mailing list: [pylons-project-security@googlegroups.com](mailto:pylons-project-security@googlegroups.com) (if security related)</p>
<p>### Thanks</p>
<p>- m4yfly and urn1ce From TianGong Team of Legendsec at Qi'anxin Group.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-icloudpd-cve-2024-49768"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-198349</id>
    <title>EUVD-2026-198349</title>
    <updated>2026-10-05T03:56:38.153890+00:00</updated>
    <content>EUVD-2026-198349</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-198349"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-49768</id>
    <title>fkie_cve-2024-49768</title>
    <updated>2026-10-05T03:56:38.153914+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. A remote client may send a request that is exactly recv_bytes (defaults to 8192) long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default) we won't read any more requests, and when the first request fails due to a parsing error, we simply close the connection. However when request lookahead is enabled, it is possible to process and receive the first request, start sending the error message back to the client while we read the next request and queue it. This will allow the secondary request to be serviced by the worker thread while the connection should be closed. Waitress 3.0.1 fixes the race condition. As a workaround, disable channel_request_lookahead, this is set to 0 by default disabling this feature.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-49768"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9298-4cf8-g4wj</id>
    <title>GHSA-9298-4cf8-g4wj — Waitress has request processing race condition in HTTP pipelining with invalid first request</title>
    <updated>2026-10-05T03:56:38.153963+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: waitress</p>
<p>### Impact</p>
<p>A remote client may send a request that is exactly `recv_bytes` (defaults to 8192) long, followed by a secondary request using HTTP pipelining.</p>
<p>When request lookahead is disabled (default) we won't read any more requests, and when the first request fails due to a parsing error, we simply close the connection.</p>
<p>However when request lookahead is enabled, it is possible to process and receive the first request, start sending the error message back to the client while we read the next request and queue it. This will allow the secondary request to be serviced by the worker thread while the connection should be closed.</p>
<p>### Patches</p>
<p>Waitress 3.0.1 fixes the race condition.</p>
<p>### Workarounds</p>
<p>Disable  `channel_request_lookahead`, this is set to `0` by default disabling this feature. For this vulnerability this value is required to be changed from the default.</p>
<p>### For more information</p>
<p>If you have any questions or comments about this advisory:
* Open an issue in https://github.com/Pylons/waitress/issues (if not sensitive or security related)
* email the Pylons Security mailing list: [pylons-project-security@googlegroups.com](mailto:pylons-project-security@googlegroups.com) (if security related)</p>
<p>### Thanks</p>
<p>- m4yfly and urn1ce From TianGong Team of Legendsec at Qi'anxin Group.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9298-4cf8-g4wj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2024-2333</id>
    <title>OESA-2024-2333 — python-waitress security update</title>
    <updated>2026-10-05T03:56:38.154037+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP3: python-waitress</p>
<p>Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on CPython on Unix and Windows under Python 2.7+ and Python 3.5+. It is also known to run on PyPy 1.6.0+ on UNIX. It supports HTTP/1.0 and HTTP/1.1.

Security Fix(es):

(CVE-2024-49768)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2024-2333"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2024-210</id>
    <title>PYSEC-2024-210</title>
    <updated>2026-10-05T03:56:38.154079+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: waitress</p>
<p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. A remote client may send a request that is exactly recv_bytes (defaults to 8192) long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default) we won't read any more requests, and when the first request fails due to a parsing error, we simply close the connection. However when request lookahead is enabled, it is possible to process and receive the first request, start sending the error message back to the client while we read the next request and queue it. This will allow the secondary request to be serviced by the worker thread while the connection should be closed. Waitress 3.0.1 fixes the race condition. As a workaround, disable channel_request_lookahead, this is set to 0 by default disabling this feature.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2024-210"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2024:10145</id>
    <title>RHSA-2024:10145 — Red Hat Security Advisory: OpenShift Container Platform 4.15.39 packages and security update</title>
    <updated>2026-10-05T03:56:38.154104+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>waitress: python-waitress: request processing race condition in HTTP pipelining with invalid first request waitress: Waitress has a denial of service leading to high CPU usage/resource exhaustion</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2024:10145"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-49768</id>
    <title>UBUNTU-CVE-2024-49768</title>
    <updated>2026-10-05T03:56:38.154124+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:24.04:LTS: waitress</p>
<p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. A remote client may send a request that is exactly recv_bytes (defaults to 8192) long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default) we won't read any more requests, and when the first request fails due to a parsing error, we simply close the connection. However when request lookahead is enabled, it is possible to process and receive the first request, start sending the error message back to the client while we read the next request and queue it. This will allow the secondary request to be serviced by the worker thread while the connection should be closed. Waitress 3.0.1 fixes the race condition. As a workaround, disable channel_request_lookahead, this is set to 0 by default disabling this feature.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-49768"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3488</id>
    <title>WID-SEC-W-2024-3488 — Red Hat OpenShift Container Platform: Mehrere Schwachstellen</title>
    <updated>2026-10-05T03:56:38.154146+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Container Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service zu verursachen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3488"/>
  </entry>
</feed>
