Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Dec 12, 2025
Updated
Oct 7, 2026
EPSS
0.5% · 45th percentile

Report tools

JSON

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.

Follow CVE-2025-67726

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
tornadowebtornado

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.

EcosystemPackageAffected rangeFix
AlmaLinux:8pcsbefore 0.10.18-2.el8_10.8.alma.10.10.18-2.el8_10.8.alma.1
AlmaLinux:8pcs-snmpbefore 0.10.18-2.el8_10.8.alma.10.10.18-2.el8_10.8.alma.1
Alpine:v3.23py3-tornadobefore 6.5.4-r06.5.4-r0
Debian:11python-tornadobefore 6.1.0-1+deb11u36.1.0-1+deb11u3
Debian:12python-tornadobefore 6.2.0-3+deb12u46.2.0-3+deb12u4
Debian:13python-tornadobefore 6.4.2-3+deb13u26.4.2-3+deb13u2
Debian:14python-tornadobefore 6.5.4-0.16.5.4-0.1
openSUSE:Leap 15.6python-tornado6before 6.3.2-150400.9.12.16.3.2-150400.9.12.1
openSUSE:Leap 15.6saltbefore 3006.0-150500.4.68.23006.0-150500.4.68.2
openSUSE:Leap 15.6salt-testbefore 3006.0-150500.4.68.13006.0-150500.4.68.1
openSUSE:Leap 16.0python-tornado6before 6.5-160000.3.16.5-160000.3.1
openSUSE:Leap 16.0saltbefore 3006.0-160000.4.13006.0-160000.4.1
openSUSE:Leap 16.0salt-testbefore 3006.0-160000.4.13006.0-160000.4.1
openSUSE:Tumbleweedpython-tornado6before 6.5.4-1.16.5.4-1.1
openSUSE:Tumbleweedsaltbefore 3006.0-55.13006.0-55.1
PyPItornadobefore 6.5.36.5.3
Red Hat:enterprise_linux:8::highavailabilitypcsbefore 0:0.10.18-2.el8_10.80:0.10.18-2.el8_10.8
Red Hat:enterprise_linux:8::highavailabilitypcs-snmpbefore 0:0.10.18-2.el8_10.80:0.10.18-2.el8_10.8
Red Hat:rhel_aus:8.4::highavailabilitypcsbefore 0:0.10.8-1.el8_4.100:0.10.8-1.el8_4.10
Red Hat:rhel_aus:8.4::highavailabilitypcs-snmpbefore 0:0.10.8-1.el8_4.100:0.10.8-1.el8_4.10
Red Hat:rhel_e4s:8.6::highavailabilitypcsbefore 0:0.10.12-6.el8_6.120:0.10.12-6.el8_6.12
Red Hat:rhel_e4s:8.6::highavailabilitypcs-snmpbefore 0:0.10.12-6.el8_6.120:0.10.12-6.el8_6.12
Red Hat:rhel_e4s:8.8::highavailabilitypcsbefore 0:0.10.15-4.el8_8.100:0.10.15-4.el8_8.10
Red Hat:rhel_e4s:8.8::highavailabilitypcs-snmpbefore 0:0.10.15-4.el8_8.100:0.10.15-4.el8_8.10

+96

Other highest-scoring records for the same primary product.

  • CVE-2024-14029Tornado before 6.4.1 HTTP Request Smuggling via Transfer-Encoding
    36Monitor
  • CVE-2023-54397Tornado before 6.3.3 HTTP Request Smuggling via Content-Length
    36Monitor
  • CVE-2026-103262Tornado before 6.5.9 Denial of Service via CurlAsyncHTTPClient
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-67724Dec 12, 2025 · Tornado vulnerable to Header Injection and XSS via reason argument
    24Monitor
  • ← EarlierCVE-2025-67725Dec 12, 2025 · Tornado is Vulnerable to Quadratic DoS via Repeated Header Coalescing
    30Monitor
  • Later →CVE-2026-31958Mar 11, 2026 · Tornado has a DoS due to too many multipart parts
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
tornadoweb tornado6.5.3 · descriptionVendor (CNA)
almalinux:pcs0.10.18-2.el8_10.8.alma.1 · AlmaLinux:8Package registry (OSV)
almalinux:pcs-snmp0.10.18-2.el8_10.8.alma.1 · AlmaLinux:8Package registry (OSV)
alpine:py3-tornado6.5.4-r0 · Alpine:v3.23Package registry (OSV)
debian:python-tornado6.2.0-3+deb12u4 · Debian:12Package registry (OSV)
opensuse:python-tornado66.3.2-150400.9.12.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:salt3006.0-150500.4.68.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:salt-test3006.0-150500.4.68.1 · openSUSE:Leap 15.6Package registry (OSV)
PyPI:tornado6.5.3Package registry (OSV)
red hat:pcs0:0.10.18-2.el8_10.8 · Red Hat:enterprise_linux:8::highavailabilityPackage registry (OSV)
red hat:pcs-snmp0:0.10.18-2.el8_10.8 · Red Hat:enterprise_linux:8::highavailabilityPackage registry (OSV)
rocky linux:pcs0:0.10.18-2.el8_10.8 · Rocky Linux:8Package registry (OSV)
suse:golang-github-lusitaniae-apache_exporter1.0.10-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:golang-github-prometheus-promu0.17.0-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:golang-github-QubitProducts-exporter_exporter0.4.0-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:python-tornado4.5.3-150000.3.13.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:python-tornado66.3.2-150400.9.12.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7Package registry (OSV)
suse:salt3006.0-150500.4.68.2 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:saltbundle-zeromq4.3.5-90002.3.6.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:saltbundlepy3.11.13-90002.4.6.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:saltbundlepy-appdirs1.4.4-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:saltbundlepy-asn1crypto1.5.1-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:saltbundlepy-atomicwrites1.1.5-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:saltbundlepy-attrs23.1.0-90002.3.3.1 · SUSE:EL-9:Update:Products:MultiLinuxManagerTools:UpdatePackage registry (OSV)
suse:venv-salt-minion3006.0-1.67.1 · SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLSPackage 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.

Finders, 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 parts
    34Monitor
  • CVE-2025-677250 days apartTornado is Vulnerable to Quadratic DoS via Repeated Header Coalescing
    30Monitor
  • CVE-2026-82397262 days apartTornado: Urlencoded body parsing omits max_num_fields, so one request can stall the event loop
    30Monitor
  • CVE-2024-52804385 days apartTornado has HTTP cookie parsing DoS vulnerability
    30Monitor
  • CVE-2026-115927318 days apartTornado: Event loop blocking and excess memory use from chunked bodies with many small chunks
    21Monitor

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

CVSS 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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records