# CVE-2024-22420: Stored cross site scripting in Markdown Preview in JupyterLab

> Attackers can execute arbitrary scripts via malicious Markdown files in JupyterLab, allowing data theft and actions as the victim.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Jan 2024
- **Updated:** 30 May 2025
- **Also known as:** BIT-jupyter-base-notebook-2024-22420, BIT-jupyter-notebook-2024-22420, BIT-jupyterlab-2024-22420, DEBIAN-CVE-2024-22420, GHSA-4m77-cmpx-vjc4, OESA-2025-1239, OESA-2025-1240, PYSEC-2026-1707, PYSEC-2026-2535, openSUSE-SU-2024:13606-1

## What is CVE-2024-22420?

CVE-2024-22420 is a medium-severity cross-site scripting vulnerability in Fedoraproject Fedora, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook and Architecture. This vulnerability depends on user interaction by opening a malicious Markdown file using JupyterLab preview feature. A malicious user can access any data that the attacked user has access to as well as perform arbitrary requests acting as the attacked user. JupyterLab version 4.0.11 has been patched. Users are advised to upgrade. Users unable to upgrade should disable the table of contents extension.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-22420?

9 open source packages ship an affected version, including jupyterlab, jupyter-base-notebook and jupyter-notebook. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jupyterlab` | Bitnami | From 4.0.0 | 4.2.4 |
| `jupyterlab` | PyPI | From 4.0.0 | 4.0.11 |
| `jupyterlab` | PyPI | From 4.0.0 | 4.0.11 |
| `jupyterlab` | PyPI | From 4.0.0 | 4.0.11 |
| `jupyter-base-notebook` | Bitnami | From 7.0.0 | None |
| `jupyter-notebook` | Bitnami | From 7.0.0 | 7.0.7 |
| `notebook` | PyPI | From 7.0.0 | 7.0.7 |
| `notebook` | PyPI | From 7.0.0 | 7.0.7 |
| `notebook` | PyPI | From 7.0.0 | 7.0.7 |

Products: Fedoraproject Fedora, Jupyter Jupyterlab, Jupyter Notebook.

## How do I fix CVE-2024-22420?

Upgrade jupyterlab to a fixed version for your release line: 4.2.4 or 4.0.11.

## Is CVE-2024-22420 being exploited?

There is no known exploitation of CVE-2024-22420 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22420 and fix it if it is affected.

What it is: CVE-2024-22420 is a medium-severity cross-site scripting vulnerability in Fedoraproject Fedora, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22420 in the wild and no public exploit code.

Affected packages and fixed versions:
- jupyterlab (Bitnami): affected from 4.0.0; fixed in 4.2.4
- jupyterlab (PyPI): affected from 4.0.0; fixed in 4.0.11
- jupyterlab (PyPI): affected from 4.0.0; fixed in 4.0.11
- jupyterlab (PyPI): affected from 4.0.0; fixed in 4.0.11
- jupyter-base-notebook (Bitnami): affected from 7.0.0; no fix listed
- jupyter-notebook (Bitnami): affected from 7.0.0; fixed in 7.0.7
- notebook (PyPI): affected from 7.0.0; fixed in 7.0.7
- notebook (PyPI): affected from 7.0.0; fixed in 7.0.7
- notebook (PyPI): affected from 7.0.0; fixed in 7.0.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-22420/ (Markdown: https://insights.sbomify.com/CVE-2024-22420/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22420
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22420
- OSV: https://osv.dev/vulnerability/CVE-2024-22420

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-22420/
Summaries are generated and may contain mistakes; the official description above is the record.