<?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-11-16T23:31:19.853507+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/brew-jupyterlab-cve-2026-116577</id>
    <title>BREW-jupyterlab-CVE-2026-116577 — Tornado: Quadratic CPU usage when parsing HTTP headers with line folding</title>
    <updated>2026-11-16T23:31:19.860907+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: jupyterlab</p>
<p>### Summary</p>
<p>Tornado's HTTP header parser takes quadratic time (O(n²)) when a header value is continued across many "obsolete line folding" (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.</p>
<p>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.</p>
<p>### Impact</p>
<p>All Tornado HTTP servers are affected. Header parsing runs before any application code, so no authentication or particular handler is required.</p>
<p>How bad it gets depends on `max_header_size`:</p>
<p>- **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.</p>
<p>Only availability is affected. Confidentiality and integrity are not.</p>
<p>### Patches</p>
<p>Fixed in Tornado 6.6 by removing support for obsolete line folding completely; header lines that begin with whitespace are now rejected.</p>
<p>### Workarounds</p>
<p>- Keep `max_header_size` at its default value or lower it. This limits the impact but doesn't remove it.
- Run Tornado behind a reverse proxy that rejects or normalizes obsolete line folding before forwarding requests.</p>
<p>### Credit</p>
<p>Repor…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-116577"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-sc17399</id>
    <title>CLEANSTART-2026-SC17399 — Tornado is a Python web framework and asynchronous networking library</title>
    <updated>2026-11-16T23:31:19.860981+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: litellm-database</p>
<p>Security vulnerability affects the litellm-database package. Tornado is a Python web framework and asynchronous networking library.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-sc17399"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-392739</id>
    <title>EUVD-2026-392739</title>
    <updated>2026-11-16T23:31:19.861004+00:00</updated>
    <content>EUVD-2026-392739</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-392739"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-116577</id>
    <title>fkie_cve-2026-116577</title>
    <updated>2026-11-16T23:31:19.861018+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Tornado is a Python web framework and asynchronous networking library. Prior to 6.6, Tornado'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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-116577"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pcg2-g6cj-q92c</id>
    <title>GHSA-pcg2-g6cj-q92c — Tornado: Quadratic CPU usage when parsing HTTP headers with line folding</title>
    <updated>2026-11-16T23:31:19.861042+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: tornado</p>
<p>### Summary</p>
<p>Tornado's HTTP header parser takes quadratic time (O(n²)) when a header value is continued across many "obsolete line folding" (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.</p>
<p>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.</p>
<p>### Impact</p>
<p>All Tornado HTTP servers are affected. Header parsing runs before any application code, so no authentication or particular handler is required.</p>
<p>How bad it gets depends on `max_header_size`:</p>
<p>- **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.</p>
<p>Only availability is affected. Confidentiality and integrity are not.</p>
<p>### Patches</p>
<p>Fixed in Tornado 6.6 by removing support for obsolete line folding completely; header lines that begin with whitespace are now rejected.</p>
<p>### Workarounds</p>
<p>- Keep `max_header_size` at its default value or lower it. This limits the impact but doesn't remove it.
- Run Tornado behind a reverse proxy that rejects or normalizes obsolete line folding before forwarding requests.</p>
<p>### Credit</p>
<p>Repor…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pcg2-g6cj-q92c"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-4798</id>
    <title>OESA-2026-4798 — python-tornado security update</title>
    <updated>2026-11-16T23:31:19.861081+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: python-tornado</p>
<p>Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed. By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.

Security Fix(es):</p>
<p>Tornado is a Python web framework and asynchronous networking library. Prior to 6.6.0, Tornado decodes HTTP/1.1 chunked transfer encoding by processing body data that has already arrived without yielding to the event loop. A remote unauthenticated peer can send millions of one-byte chunks to monopolize the process event loop and stall every other connection served by that process, while lowering max_body_size only limits the duration of each request. For handlers that do not use @stream_request_body, retaining each chunk as a separate object can consume roughly twenty times the received body size, and SimpleAsyncHTTPClient has the same event-loop behavior when reading a response from a malicious server. This issue is fixed in version 6.6.0.(CVE-2026-115927)</p>
<p>Tornado is a Python web framework and asynchronous networking library. Prior to 6.6, Tornado&amp;apos;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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-4798"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-116577</id>
    <title>UBUNTU-CVE-2026-116577</title>
    <updated>2026-11-16T23:31:19.861116+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: python-tornado, Ubuntu:Pro:18.04:LTS: python-tornado, Ubuntu:Pro:20.04:LTS: python-tornado, Ubuntu:Pro:22.04:LTS: python-tornado, Ubuntu:24.04:LTS: python-tornado, Ubuntu:26.10: python-tornado, Ubuntu:26.04:LTS: python-tornado</p>
<p>Tornado is a Python web framework and asynchronous networking library. Prior to 6.6, Tornado'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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-116577"/>
  </entry>
</feed>
