CVE-2026-49855: Jupyterlab · tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb)
Affects jupyterlabSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 4.5.8 soon.
Data as of 30 Oct 2026, 08:46 UTC
- Patch
- Available – fixed in 4.5.8
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 14 Jul 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.5.8.
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
This vulnerability is fixed in JupyterLab version 4.5.8. Users should upgrade to this version or later. Until upgrading, mitigation options include setting decompress_response=False or using CurlAsyncHTTPClient instead of the default SimpleAsyncHTTPClient to avoid unbounded memory consumption.
Description
A vulnerability in JupyterLab's use of Tornado's AsyncHTTPClient allows a malicious server to cause excessive memory consumption via decompressed gzip chunks without a size limit. This can lead to denial of service due to resource exhaustion. The issue affects versions from 1.2.0 up to but not including 4.5.8 and is fixed in version 4.5.8.