Skip to main content
VulnerabilityPublished Updated

CVE-2026-82397: Tornado · Urlencoded body parsing omits max_num_fields, so one request can stall the event loop

Affects snakevizSource GCVE Database

0
Compare
Authoritative record:CVE-2026-82397· High 7.5

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

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Aug 2026

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

Affected software

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

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

Community reviews

Loading reviews…