VulnerabilityPublished 13 Aug 2026Updated 29 Oct 2026

CVE-2026-31958: Jupyterlab · Tornado is vulnerable to DoS due to too many multipart parts

Affects jupyterlabSource GCVE Database

Compare

Authoritative record:CVE-2026-31958· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 4.5.6 soon.

Data as of 30 Oct 2026, 08:59 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 4.5.6

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade jupyterlab to 4.5.6.

Affected software

Product	Affected	Fixed in
Homebrewjupyterlab`pkg:brew/jupyterlab`Other threats	Affected >=1.2.0 <4.5.6	Fixed in 4.5.6

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

AI-suggested

Upgrade to Tornado version 6.5.5 or later, which includes new configurable limits on multipart body size and complexity to prevent this DoS condition. If multipart parsing is not required, it can be disabled entirely using the new configuration options. No other immediate actions are required once the upgrade is applied.

Description

Tornado versions prior to 6.5.5 used by JupyterLab are vulnerable to a denial-of-service (DoS) condition due to unbounded parsing of multipart/form-data requests. The vulnerability arises because the number of multipart parts is only limited by the max_body_size setting, allowing attackers to cause high CPU usage by sending requests with many parts. Tornado 6.5.5 introduces configurable limits on multipart body size and complexity, including a default limit of 100 parts per request, and allows disabling multipart parsing if not needed.

Impact

An attacker can cause a denial-of-service condition by sending HTTP requests with a large number of multipart parts, leading to high CPU usage and blocking the main thread. This impacts availability but does not affect confidentiality or integrity. There are no known exploits in the wild as of the published date.

Summary

CVE-2026-31958 affects Tornado versions before 6.5.5, where multipart/form-data parsing occurs synchronously on the main thread without sufficient limits on the number of parts. This can lead to denial-of-service by exhausting CPU resources when processing requests with many multipart parts. The vulnerability is addressed in Tornado 6.5.5 by adding configurable limits on multipart body size and complexity, including a default cap of 100 parts per request, and the option to disable multipart parsing entirely.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 08:59 UTC

Technical details

References

Community reviews

Related threats