# What is CVE-2024-43805?

> CVE-2024-43805 is a medium-severity flaw (CVSS 6.1) in Jupyterlab, published on 28 August 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.4%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2024-43805

## At a glance

- **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
- **Precursor Intelligence risk score:** 46 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** Medium (CVSS 6.1 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 0.4% (latest exploit-likelihood forecast)
- **Published:** 28 August 2024
- **Record last updated:** 17 June 2026
- **Main product:** Jupyterlab
- **Affected products:** 2

## What is CVE-2024-43805? In plain terms

It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data.

### The official description

jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. This vulnerability depends on user interaction by opening a malicious notebook with Markdown cells, or 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 v3.6.8, v4.2.5 and Jupyter Notebook v7.2.2 have been patched to resolve this issue. Users are advised to upgrade. There is no workaround for the underlying DOM Clobbering susceptibility. However, select plugins can be disabled on deployments which cannot update in a timely fashion to minimise the risk. These are: 1. `@jupyterlab/mathjax-extension:plugin` - users will loose ability to preview mathematical equations. 2. `@jupyterlab/markdownviewer-extension:plugin` - users will loose ability to open Markdown previews. 3. `@jupyterlab/mathjax2-extension:plugin` (if installed with optional `jupyterlab-mathjax2` package) - an older version of the mathjax plugin for JupyterLab 4.x. To disable these extensions run: ```jupyter labextension disable @jupyterlab/markdownviewer-extension:plugin && jupyter labextension disable @jupyterlab/mathjax-extension:plugin && jupyter labextension disable @jupyterlab/mathjax2-extension:plugin ``` in bash.

### What kind of flaw is it?

- CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: Yes, a person has to take an action
- What an attacker gets: Can read some data and change some data

Severity vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`

## Is CVE-2024-43805 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 0.4%, 0.4%, 0.4%, 0.4%, 0.4%, 0.4%, 0.4%.

### Timeline

- 28 August 2024: Published
- 17 June 2026: Record last updated

### How Precursor Intelligence ranks it

CVE-2024-43805 scores **46 out of 100 (Medium)**, with the action "Plan remediation".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2024-43805?

The published record lists 2 products. Versions are as published: "before 3.6.8" means every version up to, but not including, 3.6.8.

- [Jupyterlab](https://www.precursorintelligence.com/product/jupyter/jupyterlab) by [Jupyter](https://www.precursorintelligence.com/vendors/jupyter) (Application): before 3.6.8, 4.0.0 to before 4.2.5
- [Notebook](https://www.precursorintelligence.com/product/jupyter/notebook) by [Jupyter](https://www.precursorintelligence.com/vendors/jupyter) (Application): 7.0.0 to before 7.2.2

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

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [github.com](https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-9q39-rmj3-p4r2) (Vendor advisory)

## Questions

### What is CVE-2024-43805?

CVE-2024-43805 is a medium-severity flaw in Jupyterlab, published on 28 August 2024. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data.

### How serious is CVE-2024-43805?

It scores 6.1 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2024-43805 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

### Is CVE-2024-43805 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2024-43805 affect?

For Jupyterlab: before 3.6.8, 4.0.0 to before 4.2.5. The record lists 2 products in all, each with its versions, under "Who is affected" on this page.

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

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2024-43805 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact

