CVE-2026-82397: Tornado · Urlencoded body parsing omits max_num_fields, so one request can stall the event loop
Affects jupyterlabSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 4.6.3 soon.
Data as of 30 Oct 2026, 08:46 UTC
- Patch
- Available – fixed in 4.6.3
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 jupyterlab to 4.6.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewjupyterlabpkg:brew/jupyterlabOther 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 4.6.3 that adds a max_num_fields limit to the URL-encoded body parser, preventing excessive field parsing. Users should upgrade to version 4.6.3 or later. The fix causes requests exceeding the limit to raise a ValueError, which maps to a 400 Bad Request response. Additionally, lowering the default maximum request body size for URL-encoded forms can help mitigate the risk. No other mitigation is required once the patch is applied.
Description
Tornado's parsing of application/x-www-form-urlencoded request bodies does not limit the number of fields parsed, allowing a specially crafted request with many separators to create tens of millions of fields. This parsing occurs synchronously on the single-threaded event loop before request handling, causing the entire server to stall and resulting in a denial of service. No authentication is required to trigger this condition if any route accepts form posts. The issue affects Tornado versions from 1.2.0 up to but not including 4.6.3 and is fixed in version 4.6.3.
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)