GHSA-qjxf-f2mg-c6mc

Tornado is vulnerable to DoS due to too many multipart parts

At a glance

Published
Updated
CVE
CVE-2026-31958
Aliases
PYSEC-2026-140
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS_V4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Description

In versions of Tornado prior to 6.5.5, the only limit on the number of parts in `multipart/form-data` is the `max_body_size` setting (default 100MB). Since parsing occurs synchronously on the main thread, this creates the possibility of denial-of-service due to the cost of parsing very large multipart bodies with many parts. Tornado 6.5.5 introduces new limits on the size and complexity of multipart bodies, including a default limit of 100 parts per request. These limits are configurable if needed; see `tornado.httputil.ParseMultipartConfig`. It is also now possible to disable `multipart/form-data` parsing entirely if it is not required for the application.

Affected packages

PackageVersions
PyPI · tornadointroduced 0, fixed 6.5.5

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database