Skip to main content
VulnerabilityPublished Updated

CVE-2025-67726: Tornado · Quadratic DoS via Crafted Multipart Parameters

Affects snakevizSource GCVE Database

0
Compare
Authoritative record:CVE-2025-67726· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.2.2_3 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.2_3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade snakeviz to 2.2.2_3.

Affected software

ProductAffectedFixed in
Homebrewsnakevizpkg:brew/snakevizOther threatsAffected
  • >=2.2.0 <2.2.2_3
Fixed in
  • 2.2.2_3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Tornado version 2.2.2_3 that fixes this vulnerability. Users should upgrade to version 2.2.2_3 or later to remediate the issue. No other mitigation or workaround is indicated by the vendor advisory.

Description

A high-severity Denial of Service (DoS) vulnerability exists in Tornado's _parseparam function in httputil.py, affecting versions >=2.2.0 and <2.2.2_3. The function inefficiently parses multipart/form-data parameters, causing CPU usage to increase quadratically when processing crafted Content-Disposition headers. This can cause the Tornado server to become unresponsive due to its single event loop design.

References

Community reviews

Loading reviews…