CVE-2026-82397: Tornado · Urlencoded body parsing omits max_num_fields, so one request can stall the event loop
Affects snakevizSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 2.2.2_5 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.2.2_5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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_5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewsnakevizpkg:brew/snakevizOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Tornado version 2.2.2_5 that adds a max_num_fields parameter to limit the number of parsed fields, preventing the event loop from stalling. Users should upgrade to version 2.2.2_5 or later. Additionally, lowering the default body size cap for urlencoded requests can help mitigate the risk. No other immediate action is required once patched.
Description
Tornado versions >=2.2.0 and <2.2.2_5 have a vulnerability in parsing application/x-www-form-urlencoded request bodies where the max_num_fields parameter is not enforced. This allows an attacker to send a specially crafted request with a large number of fields, causing the synchronous parsing on the single-threaded event loop to stall and result in a denial of service for the entire server process. The issue is fixed in version 2.2.2_5.
References
- github.com/tornadoweb/tornado/security/advisories/GHSA-mpf4-983q-p7j4 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-82397 (opens in a new tab)
- github.com/tornadoweb/tornado/pull/3704 (opens in a new tab)
- github.com/tornadoweb/tornado/commit/8d6363ed7b69d5f0da806efe34d256627a2191de (opens in a new tab)
- github.com/tornadoweb/tornado (opens in a new tab)
- github.com/tornadoweb/tornado/releases/tag/v6.5.8 (opens in a new tab)