CVE-2024-43805 | HTML injection in Jupyter Notebook and JupyterLab leading to DOM Clobbering

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.

Published: 2024-08-28 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-43805 is rated Moderate Risk (52.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.43%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-43805

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-17 0.32% 0.43% +0.11%
2 2025-12-16 0.20% 0.32% +0.11%
3 2025-11-21 0.20%

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-43805

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.6 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
2.8 4.7 [email protected]
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 2.7 [email protected]

Weakness enumeration for CVE-2024-43805

GitHub Security Advisory for CVE-2024-43805

GHSA-9q39-rmj3-p4r2 · Severity: high · Ecosystem: pip — HTML injection in Jupyter Notebook and JupyterLab leading to DOM Clobbering

OS Trackers for CVE-2024-43805

vendor priority summary link
alpine high CVE-2024-43805: 1 source package rows (jupyterlab); 15 state rows across 2 repos (3.23-community, edge-community); fixed 0, open 15. https://security.alpinelinux.org/vuln/CVE-2024-43805
debian unimportant CVE-2024-43805 unimportant priority: Debian including 2 source packages (jupyter-notebook, jupyterlab), 8 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 8. https://security-tracker.debian.org/tracker/CVE-2024-43805
suse high https://www.suse.com/security/cve/CVE-2024-43805/
ubuntu medium CVE-2024-43805 medium priority: Ubuntu including 2 source packages (jupyter-notebook, jupyterlab), 15 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream): not-affected 7, DNE 3, ignored 2, needs-triage 2, released 1. https://ubuntu.com/security/CVE-2024-43805

Affected software / configurations for CVE-2024-43805

Vendor Product Version Raw CPE
jupyter jupyterlab < 3.6.8 cpe:2.3:a:jupyter:jupyterlab:*:*:*:*:*:*:*:*
jupyter jupyterlab >= 4.0.0, < 4.2.5 cpe:2.3:a:jupyter:jupyterlab:*:*:*:*:*:*:*:*
jupyter notebook >= 7.0.0, < 7.2.2 cpe:2.3:a:jupyter:notebook:*:*:*:*:*:*:*:*

References for CVE-2024-43805

cvelogic Threat Intelligence