<?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>Fri, 30 Oct 2026 13:28:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-116577 — Tornado: Quadratic CPU usage when parsing HTTP headers with line folding</title>
      <link>https://db.gcve.eu/vuln/cve-2026-116577</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tornadoweb tornado&lt;/p&gt;
&lt;p&gt;Tornado is a Python web framework and asynchronous networking library. Prior to 6.6, Tornado&amp;#39;s HTTP header parser accepts obsolete line folding and repeatedly concatenates short continuation lines, causing quadratic CPU consumption on the IOLoop thread. An unauthenticated client can submit a header block containing many obsolete line-folding continuations before application code runs, blocking other connections served by the process. The cost grows with max_header_size, and only availability is affected. This issue is fixed in version 6.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; tornadoweb tornado&lt;/p&gt;
&lt;p&gt;Tornado is a Python web framework and asynchronous networking library. Prior to 6.6, Tornado&amp;#39;s HTTP header parser accepts obsolete line folding and repeatedly concatenates short continuation lines, causing quadratic CPU consumption on the IOLoop thread. An unauthenticated client can submit a header block containing many obsolete line-folding continuations before application code runs, blocking other connections served by the process. The cost grows with max_header_size, and only availability is affected. This issue is fixed in version 6.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-116577</guid>
    </item>
    <item>
      <title>GHSA-pcg2-g6cj-q92c — Tornado: Quadratic CPU usage when parsing HTTP headers with line folding</title>
      <link>https://db.gcve.eu/vuln/ghsa-pcg2-g6cj-q92c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tornado&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Tornado&amp;#39;s HTTP header parser takes quadratic time (O(n²)) when a header value is continued across many &amp;#34;obsolete line folding&amp;#34; (obs-fold) lines. An unauthenticated attacker can send a request whose header block is mostly short continuation lines. Parsing it uses a large amount of CPU on the IOLoop thread and blocks every other connection that process is serving.&lt;/p&gt;
&lt;p&gt;This issue is closely related to CVE-2025-67725 (GHSA-c98p-7wgm-6p64). The fix for that advisory covered repeated headers but not line-folded continuations.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All Tornado HTTP servers are affected. Header parsing runs before any application code, so no authentication or particular handler is required.&lt;/p&gt;
&lt;p&gt;How bad it gets depends on `max_header_size`:&lt;/p&gt;
&lt;p&gt;- **Default (64 KB):** each malicious request blocks the event loop for tens of milliseconds. Repeated requests can degrade service.
- **Raised `max_header_size`:** the cost grows with the square of the header size. A single 1 MB request can block the process for several seconds.&lt;/p&gt;
&lt;p&gt;Only availability is affected. Confidentiality and integrity are not.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in Tornado 6.6 by removing support for obsolete line folding completely; header lines that begin with whitespace are now rejected.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;- Keep `max_header_size` at its default value or lower it. This limits the impact but doesn&amp;#39;t remove it.
- Run Tornado behind a reverse proxy that rejects or normalizes obsolete line folding before forwarding requests.&lt;/p&gt;
&lt;p&gt;### Credit&lt;/p&gt;
&lt;p&gt;Repor…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: tornado&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Tornado&amp;#39;s HTTP header parser takes quadratic time (O(n²)) when a header value is continued across many &amp;#34;obsolete line folding&amp;#34; (obs-fold) lines. An unauthenticated attacker can send a request whose header block is mostly short continuation lines. Parsing it uses a large amount of CPU on the IOLoop thread and blocks every other connection that process is serving.&lt;/p&gt;
&lt;p&gt;This issue is closely related to CVE-2025-67725 (GHSA-c98p-7wgm-6p64). The fix for that advisory covered repeated headers but not line-folded continuations.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All Tornado HTTP servers are affected. Header parsing runs before any application code, so no authentication or particular handler is required.&lt;/p&gt;
&lt;p&gt;How bad it gets depends on `max_header_size`:&lt;/p&gt;
&lt;p&gt;- **Default (64 KB):** each malicious request blocks the event loop for tens of milliseconds. Repeated requests can degrade service.
- **Raised `max_header_size`:** the cost grows with the square of the header size. A single 1 MB request can block the process for several seconds.&lt;/p&gt;
&lt;p&gt;Only availability is affected. Confidentiality and integrity are not.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in Tornado 6.6 by removing support for obsolete line folding completely; header lines that begin with whitespace are now rejected.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;- Keep `max_header_size` at its default value or lower it. This limits the impact but doesn&amp;#39;t remove it.
- Run Tornado behind a reverse proxy that rejects or normalizes obsolete line folding before forwarding requests.&lt;/p&gt;
&lt;p&gt;### Credit&lt;/p&gt;
&lt;p&gt;Repor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-pcg2-g6cj-q92c</guid>
    </item>
  </channel>
</rss>
