CVE-2024-22420: jupyterlab · Cross-site Scripting
Affects jupyterlabSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.0.11 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.11
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade jupyterlab to 4.0.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIjupyterlabpkg:pypi/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 patch is available in JupyterLab version 4.0.11. Users should upgrade to this version or later to remediate the vulnerability. As a workaround, users can disable the table of contents extension by running 'jupyter labextension disable @jupyterlab/toc-extension:registry'.
Description
CVE-2024-22420 is a cross-site scripting (XSS) vulnerability in JupyterLab that arises from improper neutralization of input during web page generation. The vulnerability can be triggered when a user opens a malicious notebook containing Markdown cells or previews a malicious Markdown file. Exploitation allows an attacker to access any data available to the victim and perform arbitrary requests on their behalf. JupyterLab version 4.0.11 includes a patch that addresses this issue. As a workaround, users can disable the table of contents extension to mitigate the risk.
References
- github.com/jupyterlab/jupyterlab/security/advisories/GHSA-4m77-cmpx-vjc4 (opens in a new tab)
- github.com/jupyterlab/jupyterlab/commit/e1b3aabab603878e46add445a3114e838411d2df (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UQJKNRDRFMKGVRIYNNN6CKMNJDNYWO2H/ (opens in a new tab)