CVE-2024-43805

Workarounds

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:

• @jupyterlab/mathjax-extension:plugin - users will loose ability to preview mathematical equations
• @jupyterlab/markdownviewer-extension:plugin - users will loose ability to open Markdown previews
• @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

To confirm that the plugins were disabled run:

jupyter labextension list

References

None

Notes

This change has a potential to break rendering of some markdown. There is a setting in Sanitizer which allows to revert to the previous sanitizer settings (allowNamedProperties).

The 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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-43805 has a CVSS score of 7.6 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.6.8, 7.2.2, 4.2.5); upgrading removes the vulnerable code path.

Kodem intelligence

JupyterLab v3.6.8, v4.2.5 and Jupyter Notebook v7.2.2 were patched.

1. What is CVE-2024-43805? CVE-2024-43805 is a high-severity cross-site scripting (XSS) vulnerability in jupyterlab (pip), affecting versions <= 3.6.7. It is fixed in 3.6.8, 7.2.2, 4.2.5. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-43805? CVE-2024-43805 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-43805?
   • jupyterlab (pip) (versions <= 3.6.7)
   • notebook (pip) (versions >= 7.0.0, <= 7.2.1)
4. Is there a fix for CVE-2024-43805? Yes. CVE-2024-43805 is fixed in 3.6.8, 7.2.2, 4.2.5. Upgrade to this version or later.
5. Is CVE-2024-43805 exploitable, and should I be worried? Whether CVE-2024-43805 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-43805 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-43805?
   • Upgrade jupyterlab to 3.6.8 or later
   • Upgrade notebook to 7.2.2 or later
   • Upgrade jupyterlab to 4.2.5 or later