CVE-2026-82397

published 31 Aug 2026 · updated 2 Sep 2026

Tornado: Urlencoded body parsing omits max_num_fields, so one request can stall the event loop

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

Tornado is a Python web framework and asynchronous networking library. Prior to 6.5.8, Tornado parses application/x-www-form-urlencoded request bodies with urllib.parse.parse_qs in tornado/escape.py without passing max_num_fields. RequestHandler._execute in tornado/web.py parses the body before handler dispatch through HTTPServerRequest._parse_body and parse_body_arguments in tornado/httputil.py, so an unauthenticated request body containing millions of separator-delimited fields can synchronously stall the single-threaded event loop and delay every connection. The body is bounded only by max_buffer_size, which defaults to 104857600 bytes. This issue is fixed in version 6.5.8.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
tornadoweb<6.5.8

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-82397 severity on Zeptric[![CVE-2026-82397](https://zeptric.io/badge/cve/CVE-2026-82397.svg)](https://zeptric.io/cve/CVE-2026-82397)