<?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://db.gcve.eu</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, 15 Nov 2026 18:36:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-103022 — Urwid: handle_short_request() crashes on non-ASCII POST body (UnicodeEncodeError DoS)</title>
      <link>https://db.gcve.eu/vuln/cve-2026-103022</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; urwid&lt;/p&gt;
&lt;p&gt;Urwid is a console user interface library for Python. Prior to 4.0.7, handle_short_request() in urwid/display/web.py performs unguarded character encoding on POST input and unguarded UTF-8 decoding on polling update socket output. A remote attacker who obtains a valid X-Urwid-ID session token can submit non-ASCII POST data that raises UnicodeEncodeError, while non-UTF-8 polling output raises UnicodeDecodeError, causing the CGI handler to return an error and terminate request processing. The POST exception path also leaves an opened file descriptor unclosed for the CGI process lifetime, so repeated requests can cause denial of service for the web display interface. This issue is fixed in version 4.0.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; urwid&lt;/p&gt;
&lt;p&gt;Urwid is a console user interface library for Python. Prior to 4.0.7, handle_short_request() in urwid/display/web.py performs unguarded character encoding on POST input and unguarded UTF-8 decoding on polling update socket output. A remote attacker who obtains a valid X-Urwid-ID session token can submit non-ASCII POST data that raises UnicodeEncodeError, while non-UTF-8 polling output raises UnicodeDecodeError, causing the CGI handler to return an error and terminate request processing. The POST exception path also leaves an opened file descriptor unclosed for the CGI process lifetime, so repeated requests can cause denial of service for the web display interface. This issue is fixed in version 4.0.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-103022</guid>
    </item>
    <item>
      <title>GHSA-cp25-j9x5-p5xm — Urwid: handle_short_request() crashes on non-ASCII POST body (UnicodeEncodeError DoS)</title>
      <link>https://db.gcve.eu/vuln/ghsa-cp25-j9x5-p5xm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: urwid&lt;/p&gt;
&lt;p&gt;### Summary
The `handle_short_request()` function in `urwid/display/web.py` raises an unhandled `UnicodeEncodeError` when processing a POST request body containing non-ASCII bytes. The function reads POST input and encodes it to ASCII before writing to a named pipe. Any byte value above `0x7F` causes the CGI process to exit with an unhandled exception, returning an HTTP 500 error to the client. Additionally, a file descriptor opened earlier in the same function is not closed before the exception propagates, causing a file descriptor leak for the lifetime of the CGI process.&lt;/p&gt;
&lt;p&gt;A second instance of missing exception handling exists in the polling update path, where non-UTF-8 socket output causes an unhandled `UnicodeDecodeError`.&lt;/p&gt;
&lt;p&gt;### Impact
An attacker who observes a valid `X-Urwid-ID` session token (transmitted in plaintext HTTP response headers) can send repeated POST requests containing non-ASCII bytes to the `urwid` CGI endpoint. Each malformed request causes the CGI handler to crash with HTTP 500. This results in a Denial of Service (DoS) for legitimate users using the `urwid` web interface.&lt;/p&gt;
&lt;p&gt;### Affected Versions
`urwid &amp;lt;= 4.0.6`&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in `urwid 4.0.7`. Users should upgrade to version `4.0.7` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
No direct workaround exists short of disabling the `urwid` web display interface.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: urwid&lt;/p&gt;
&lt;p&gt;### Summary
The `handle_short_request()` function in `urwid/display/web.py` raises an unhandled `UnicodeEncodeError` when processing a POST request body containing non-ASCII bytes. The function reads POST input and encodes it to ASCII before writing to a named pipe. Any byte value above `0x7F` causes the CGI process to exit with an unhandled exception, returning an HTTP 500 error to the client. Additionally, a file descriptor opened earlier in the same function is not closed before the exception propagates, causing a file descriptor leak for the lifetime of the CGI process.&lt;/p&gt;
&lt;p&gt;A second instance of missing exception handling exists in the polling update path, where non-UTF-8 socket output causes an unhandled `UnicodeDecodeError`.&lt;/p&gt;
&lt;p&gt;### Impact
An attacker who observes a valid `X-Urwid-ID` session token (transmitted in plaintext HTTP response headers) can send repeated POST requests containing non-ASCII bytes to the `urwid` CGI endpoint. Each malformed request causes the CGI handler to crash with HTTP 500. This results in a Denial of Service (DoS) for legitimate users using the `urwid` web interface.&lt;/p&gt;
&lt;p&gt;### Affected Versions
`urwid &amp;lt;= 4.0.6`&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in `urwid 4.0.7`. Users should upgrade to version `4.0.7` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
No direct workaround exists short of disabling the `urwid` web display interface.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-cp25-j9x5-p5xm</guid>
    </item>
  </channel>
</rss>
