<?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-28T23:16:00.108181+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/cve-2022-31015</id>
    <title>CVE-2022-31015 — Uncaught Exception (due to a data race) leads to process termination in Waitress</title>
    <updated>2026-09-28T23:16:00.110681+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Pylons waitress</p>
<p>Waitress is a Web Server Gateway Interface server for Python 2 and 3. Waitress versions 2.1.0 and 2.1.1 may terminate early due to a thread closing a socket while the main thread is about to call select(). This will lead to the main thread raising an exception that is not handled and then causing the entire application to be killed. This issue has been fixed in Waitress 2.1.2 by no longer allowing the WSGI thread to close the socket. Instead, that is always delegated to the main thread. There is no work-around for this issue. However, users using waitress behind a reverse proxy server are less likely to have issues if the reverse proxy always reads the full response.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-31015"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-f5x9-8jwc-25rw</id>
    <title>GHSA-f5x9-8jwc-25rw — Uncaught Exception (due to a data race) leads to process termination in Waitress</title>
    <updated>2026-09-28T23:16:00.110785+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>Waitress may terminate early due to a thread closing a socket while the main thread is about to call select(). This will lead to the main thread raising an exception that is not handled and then causing the entire application to be killed.</p>
<p>### Patches</p>
<p>This issue has been fixed in Waitress 2.1.2 by no longer allowing the WSGI thread to close the socket, instead it is always delegated to the main thread.</p>
<p>### Workarounds</p>
<p>There is no work-around, however users using waitress behind a reverse proxy server are less likely to have issues if the reverse proxy always reads the full response.</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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-f5x9-8jwc-25rw"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2022-205</id>
    <title>PYSEC-2022-205</title>
    <updated>2026-09-28T23:16:00.110852+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. Waitress versions 2.1.0 and 2.1.1 may terminate early due to a thread closing a socket while the main thread is about to call select(). This will lead to the main thread raising an exception that is not handled and then causing the entire application to be killed. This issue has been fixed in Waitress 2.1.2 by no longer allowing the WSGI thread to close the socket. Instead, that is always delegated to the main thread. There is no work-around for this issue. However, users using waitress behind a reverse proxy server are less likely to have issues if the reverse proxy always reads the full response.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2022-205"/>
  </entry>
</feed>
