# CVE-2026-31958: Tornado has a DoS due to too many multipart parts > Attackers can cause denial of service in Tornado web framework by sending multipart requests with excessive parts, blocking the main thread. - **Severity:** High 8.7 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Mar 2026 - **Updated:** 1 Apr 2026 - **Also known as:** ALSA-2026:8093, BELL-CVE-2026-31958, CLEANSTART-2026-KC70248, CLEANSTART-2026-TN75201, DEBIAN-CVE-2026-31958, ECHO-5939-f806-1836, GHSA-qjxf-f2mg-c6mc, MINI-8jw5-h5rw-7f56, MINI-ffcm-3cr9-rp48, MINI-pc2r-4mwh-pjvc, MINI-qf5p-g9wx-qc42, OESA-2026-1673, OESA-2026-1674, OESA-2026-1675, OESA-2026-1676, OESA-2026-1677, OESA-2026-1995, PYSEC-2026-140, RHSA-2026:8093, RLSA-2026:8093, ROOT-APP-PYPI-CVE-2026-31958, SUSE-SU-2026:1064-1, SUSE-SU-2026:1171-1, SUSE-SU-2026:1519-1, SUSE-SU-2026:1520-1, SUSE-SU-2026:1521-1, SUSE-SU-2026:1523-1, SUSE-SU-2026:1525-1, SUSE-SU-2026:20761-1, SUSE-SU-2026:20770-1, SUSE-SU-2026:20797-1, SUSE-SU-2026:20919-1, SUSE-SU-2026:21993-1, SUSE-SU-2026:2252-1, SUSE-SU-2026:2256-1, SUSE-SU-2026:2257-1, UBUNTU-CVE-2026-31958, openSUSE-SU-2026:10374-1, openSUSE-SU-2026:20406-1, openSUSE-SU-2026:20918-1 ## What is CVE-2026-31958? CVE-2026-31958 is a high-severity denial of service vulnerability in tornadoweb tornado, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Tornado is a Python web framework and asynchronous networking library. 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. This vulnerability is fixed in 6.5.5. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-31958? 3 open source packages ship an affected version, including tornado. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tornado` | PyPI | All versions | 6.5.5 | | `tornado` | PyPI | All versions | 6.5.5 | | `tornado` | PyPI | All versions | 6.5.5 | | `pcs` | AlmaLinux:8 | All versions | 0.10.18-2.el8_10.9.alma.1 | | `pcs-snmp` | AlmaLinux:8 | All versions | 0.10.18-2.el8_10.9.alma.1 | | `pcs` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:0.10.18-2.el8_10.9 | | `pcs-snmp` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:0.10.18-2.el8_10.9 | | `pcs` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:0.10.18-2.el8_10.9 | | `pcs-snmp` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:0.10.18-2.el8_10.9 | | `pcs` | Rocky Linux:8 | All versions | 0:0.10.18-2.el8_10.9 | | `golang-github-lusitaniae-apache_exporter` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 1.0.10-90002.3.6.1 | | `saltbundlepy` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 3.11.13-90002.4.9.1 | | `saltbundlepy-core` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 3.11.13-90002.4.9.1 | | `saltbundlepy-m2crypto` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 0.45.1-90002.3.9.2 | | `saltbundlepy-pyzmq` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 25.1.2-90002.3.9.1 | | `saltbundlepy-simplejson` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 3.19.1-90002.3.6.1 | | `saltbundlepy-tornado` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 6.3.2-90002.4.6.2 | | `spacecmd` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 5.1.13-90002.3.9.1 | | `uyuni-tools` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 5.1.26-90002.3.9.1 | | `venv-salt-minion` | SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | All versions | 3006.0-90002.5.12.2 | | `python-tornado` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 4.5.3-150000.3.19.1 | | `python-tornado6` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 6.3.2-150400.9.15.1 | | `python-tornado` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 4.5.3-150000.3.19.1 | | `python-tornado6` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 6.3.2-150400.9.15.1 | | `python-tornado` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 4.5.3-150000.3.19.1 | | `python-tornado6` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 6.3.2-150400.9.15.1 | | `python-tornado` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 4.5.3-150000.3.19.1 | | `python-tornado6` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 6.3.2-150400.9.15.1 | | `python-tornado` | SUSE:Linux Enterprise Micro 5.2 | All versions | 4.5.3-150000.3.19.1 | | `python-tornado` | SUSE:Linux Enterprise Micro 5.3 | All versions | 4.5.3-150000.3.19.1 | | `python-tornado` | SUSE:Linux Enterprise Micro 5.4 | All versions | 4.5.3-150000.3.19.1 | | `python-tornado` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.5.3-150000.3.19.1 | | `python-tornado` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 4.5.3-150000.3.19.1 | | `python-tornado6` | SUSE:Linux Enterprise Module for Python 3 15 SP7 | All versions | 6.3.2-150400.9.15.1 | | `python-tornado` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 4.5.3-150000.3.19.1 | | `python-tornado6` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 6.3.2-150400.9.15.1 | | `python-tornado` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 4.5.3-150000.3.19.1 | | `python-tornado6` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 6.3.2-150400.9.15.1 | | `python-tornado` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 4.5.3-150000.3.19.1 | | `python-tornado6` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 6.3.2-150400.9.15.1 | Products: Tornadoweb Tornado. ## How do I fix CVE-2026-31958? Upgrade tornado to 6.5.5 or later. ## Is CVE-2026-31958 being exploited? There is no known exploitation of CVE-2026-31958 in the wild and no public exploit code. ## Other vulnerabilities in tornadoweb tornado - [CVE-2025-67725](https://insights.sbomify.com/CVE-2025-67725/): Tornado is Vulnerable to Quadratic DoS via Repeated Header Coalescing (high 7.5) - [CVE-2025-67726](https://insights.sbomify.com/CVE-2025-67726/): Tornado is Vulnerable to Quadratic DoS via Crafted Multipart Parameters (high 7.5) - [CVE-2024-52804](https://insights.sbomify.com/CVE-2024-52804/): Tornado has HTTP cookie parsing DoS vulnerability (high 7.5) - [CVE-2026-35536](https://insights.sbomify.com/CVE-2026-35536/): Tornado has incomplete validation of cookie attributes (high 7.2) - [CVE-2014-9720](https://insights.sbomify.com/CVE-2014-9720/): Tornado XSRF cookie allows side-channel attack against TLS (BREACH attack) (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-31958 and fix it if it is affected. What it is: CVE-2026-31958 is a high-severity denial of service vulnerability in tornadoweb tornado, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-31958 in the wild and no public exploit code. Affected packages and fixed versions: - tornado (PyPI): affected all versions; fixed in 6.5.5 - tornado (PyPI): affected all versions; fixed in 6.5.5 - tornado (PyPI): affected all versions; fixed in 6.5.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-31958/ (Markdown: https://insights.sbomify.com/CVE-2026-31958/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31958 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31958 - OSV: https://osv.dev/vulnerability/CVE-2026-31958 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-31958/ Summaries are generated and may contain mistakes; the official description above is the record.