CVE-2025-67726: Tornado is Vulnerable to Quadratic DoS via Crafted Multipart Parameters
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: tornadoweb tornado 6.5.3.
Low priority for now. Upgrade to tornadoweb tornado 6.5.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Tornado is a Python web framework and asynchronous networking library. Versions 6.5.2 and below use an inefficient algorithm when parsing parameters for HTTP header values, potentially causing a DoS. The _parseparam function in httputil.py is used to parse specific HTTP header values, such as those in multipart/form-data and repeatedly calls string.count() within a nested loop while processing quoted semicolons. If an attacker sends a request with a large number of maliciously crafted parameters in a Content-Disposition header, the server's CPU usage increases quadratically (O(n²)) during parsing. Due to Tornado's single event loop architecture, a single malicious request can cause the entire server to become unresponsive for an extended period. This issue is fixed in version 6.5.3.
- BDU:2026-02928
- GHSA-jhmp-mqwm-3gq8
- ALSA-2026:0930
- DLA-4461-1
- openSUSE-SU-2025:15838-1
- openSUSE-SU-2026:10110-1
- openSUSE-SU-2026:20015-1
- openSUSE-SU-2026:20412-1
- PYSEC-2025-267
- RHSA-2026:0930
- RHSA-2026:2462
- RHSA-2026:2465
- RHSA-2026:2469
- RHSA-2026:2484
- RLSA-2026:0930
- SUSE-EL-9-CLIENT-TOOLS-2026-1026
- SUSE-SU-2026:0010-1
- SUSE-SU-2026:0222-1
- SUSE-SU-2026:0623-1
- SUSE-SU-2026:0625-1
- Published
- Dec 12, 2025
- Updated
- Oct 7, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- CWE-400
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| tornadoweb | tornado | cpe:2.3:a:tornadoweb:tornado |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tornadoweb tornadobefore 6.5.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
tornadoweb tornado
- < 6.5.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | pcs | before 0.10.18-2.el8_10.8.alma.1 | 0.10.18-2.el8_10.8.alma.1 |
| AlmaLinux:8 | pcs-snmp | before 0.10.18-2.el8_10.8.alma.1 | 0.10.18-2.el8_10.8.alma.1 |
| Alpine:v3.23 | py3-tornado | before 6.5.4-r0 | 6.5.4-r0 |
| Debian:11 | python-tornado | before 6.1.0-1+deb11u3 | 6.1.0-1+deb11u3 |
| Debian:12 | python-tornado | before 6.2.0-3+deb12u4 | 6.2.0-3+deb12u4 |
| Debian:13 | python-tornado | before 6.4.2-3+deb13u2 | 6.4.2-3+deb13u2 |
| Debian:14 | python-tornado | before 6.5.4-0.1 | 6.5.4-0.1 |
| openSUSE:Leap 15.6 | python-tornado6 | before 6.3.2-150400.9.12.1 | 6.3.2-150400.9.12.1 |
| openSUSE:Leap 15.6 | salt | before 3006.0-150500.4.68.2 | 3006.0-150500.4.68.2 |
| openSUSE:Leap 15.6 | salt-test | before 3006.0-150500.4.68.1 | 3006.0-150500.4.68.1 |
| openSUSE:Leap 16.0 | python-tornado6 | before 6.5-160000.3.1 | 6.5-160000.3.1 |
| openSUSE:Leap 16.0 | salt | before 3006.0-160000.4.1 | 3006.0-160000.4.1 |
| openSUSE:Leap 16.0 | salt-test | before 3006.0-160000.4.1 | 3006.0-160000.4.1 |
| openSUSE:Tumbleweed | python-tornado6 | before 6.5.4-1.1 | 6.5.4-1.1 |
| openSUSE:Tumbleweed | salt | before 3006.0-55.1 | 3006.0-55.1 |
| PyPI | tornado | before 6.5.3 | 6.5.3 |
| Red Hat:enterprise_linux:8::highavailability | pcs | before 0:0.10.18-2.el8_10.8 | 0:0.10.18-2.el8_10.8 |
| Red Hat:enterprise_linux:8::highavailability | pcs-snmp | before 0:0.10.18-2.el8_10.8 | 0:0.10.18-2.el8_10.8 |
| Red Hat:rhel_aus:8.4::highavailability | pcs | before 0:0.10.8-1.el8_4.10 | 0:0.10.8-1.el8_4.10 |
| Red Hat:rhel_aus:8.4::highavailability | pcs-snmp | before 0:0.10.8-1.el8_4.10 | 0:0.10.8-1.el8_4.10 |
| Red Hat:rhel_e4s:8.6::highavailability | pcs | before 0:0.10.12-6.el8_6.12 | 0:0.10.12-6.el8_6.12 |
| Red Hat:rhel_e4s:8.6::highavailability | pcs-snmp | before 0:0.10.12-6.el8_6.12 | 0:0.10.12-6.el8_6.12 |
| Red Hat:rhel_e4s:8.8::highavailability | pcs | before 0:0.10.15-4.el8_8.10 | 0:0.10.15-4.el8_8.10 |
| Red Hat:rhel_e4s:8.8::highavailability | pcs-snmp | before 0:0.10.15-4.el8_8.10 | 0:0.10.15-4.el8_8.10 |
+96
Same product
tornadoweb: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-14029Tornado before 6.4.1 HTTP Request Smuggling via Transfer-Encoding36Monitor
- CVE-2023-54397Tornado before 6.3.3 HTTP Request Smuggling via Content-Length36Monitor
- CVE-2026-103262Tornado before 6.5.9 Denial of Service via CurlAsyncHTTPClient34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-67724Dec 12, 2025 · Tornado vulnerable to Header Injection and XSS via reason argument24Monitor
- ← EarlierCVE-2025-67725Dec 12, 2025 · Tornado is Vulnerable to Quadratic DoS via Repeated Header Coalescing30Monitor
- Later →CVE-2026-31958Mar 11, 2026 · Tornado has a DoS due to too many multipart parts34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| tornadoweb tornado | 6.5.3 · description | Vendor (CNA) |
| almalinux:pcs | 0.10.18-2.el8_10.8.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:pcs-snmp | 0.10.18-2.el8_10.8.alma.1 · AlmaLinux:8 | Package registry (OSV) |
| alpine:py3-tornado | 6.5.4-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:python-tornado | 6.2.0-3+deb12u4 · Debian:12 | Package registry (OSV) |
| opensuse:python-tornado6 | 6.3.2-150400.9.12.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:salt | 3006.0-150500.4.68.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:salt-test | 3006.0-150500.4.68.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| PyPI:tornado | 6.5.3 | Package registry (OSV) |
| red hat:pcs | 0:0.10.18-2.el8_10.8 · Red Hat:enterprise_linux:8::highavailability | Package registry (OSV) |
| red hat:pcs-snmp | 0:0.10.18-2.el8_10.8 · Red Hat:enterprise_linux:8::highavailability | Package registry (OSV) |
| rocky linux:pcs | 0:0.10.18-2.el8_10.8 · Rocky Linux:8 | Package registry (OSV) |
| suse:golang-github-lusitaniae-apache_exporter | 1.0.10-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:golang-github-prometheus-promu | 0.17.0-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:golang-github-QubitProducts-exporter_exporter | 0.4.0-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:python-tornado | 4.5.3-150000.3.13.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:python-tornado6 | 6.3.2-150400.9.12.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7 | Package registry (OSV) |
| suse:salt | 3006.0-150500.4.68.2 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:saltbundle-zeromq | 4.3.5-90002.3.6.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy | 3.11.13-90002.4.6.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-appdirs | 1.4.4-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-asn1crypto | 1.5.1-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-atomicwrites | 1.1.5-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-attrs | 23.1.0-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:venv-salt-minion | 3006.0-1.67.1 · SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-3195889 days apartTornado has a DoS due to too many multipart parts34Monitor
- CVE-2025-677250 days apartTornado is Vulnerable to Quadratic DoS via Repeated Header Coalescing30Monitor
- CVE-2026-82397262 days apartTornado: Urlencoded body parsing omits max_num_fields, so one request can stall the event loop30Monitor
- CVE-2024-52804385 days apartTornado has HTTP cookie parsing DoS vulnerability30Monitor
- CVE-2026-115927318 days apartTornado: Event loop blocking and excess memory use from chunked bodies with many small chunks21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.