Is jupyterlab 2.0 vulnerable?
PyPI · 3 releases from 2.0.0 to 2.0.2 · latest jupyterlab is 4.6.6 · checked 18 Nov 2026
Yes: 10 known advisories
Yes. jupyterlab 2.0.2, the last 2.0 release, is affected by 10 known security advisories (5 high, 2 medium, 3 low), including CVE-2026-73415, CVE-2026-42557, CVE-2026-40171. Upgrade to 4.5.10 or later to fix all of them.
pip install 'jupyterlab>=4.5.10'Is your project on an affected jupyterlab?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting jupyterlab 2.0.2
JupyterLab: Image viewer allows XSS when opening malicious image in new browser tab
- Affected
- >=4.6.0 <4.6.2 · <4.5.10
- Fixed in
- 4.5.10, 4.6.2
JupyterLab: Allowlist/blocklist check in `PyPIExtensionManager.install()` not enforced for direct callers (missing `await`)
- Affected
- >=4.6.0 <4.6.2 · <4.5.10
- Fixed in
- 4.5.10, 4.6.2
JupyterLab: Stored XSS in extension manager through package metadata unsanitized URI protocol
- Affected
- <4.5.9
- Fixed in
- 4.5.9
JupyterLab's command linker attributes in HTML enable one-click command execution from untrusted content
- Affected
- <4.5.7
- Fixed in
- 4.5.7
Jupyter Notebook Vulnerable to Authentication Token Theft via CommandLinker XSS
- Affected
- <4.5.7
- Fixed in
- 4.5.7
JupyterLab LaTeX typesetter links did not enforce `noopener` attribute
- Affected
- <4.4.8
- Fixed in
- 4.4.8
HTML injection in Jupyter Notebook and JupyterLab leading to DOM Clobbering
- Affected
- <3.6.8 · >=4.0.0 <4.2.5
- Fixed in
- 3.6.8, 4.2.5
No summary published
- Affected
- <4.3.0
- Fixed in
- 4.3.0
JupyterLab vulnerable to potential authentication and CSRF tokens leak
- Affected
- >=4.0.0 <4.0.11 · <3.6.7
- Fixed in
- 3.6.7, 4.0.11
JupyterLab: XSS due to lack of sanitization of the action attribute of an html <form>
- Affected
- <1.2.21 · >=2.0.0a0 <2.2.10 · >=2.3.0a0 <2.3.2 · >=3.0.0a0 <3.0.17 · >=3.1.0a0 <3.1.4
- Fixed in
- 1.2.21, 2.2.10, 2.3.2, 3.0.17, 3.1.4
Every jupyterlab 2.0.x release
Affected: 2.0.0 to 2.0.2. Latest jupyterlab: 4.6.6.
| Version | Known advisories |
|---|---|
| jupyterlab 2.0.2 | CVE-2026-73415, CVE-2026-73626, CVE-2026-67338, CVE-2026-42557, CVE-2026-40171, CVE-2025-59842, CVE-2024-43805, CVE-2024-39700, CVE-2024-22421, CVE-2021-32797 |
| jupyterlab 2.0.1 | CVE-2026-73415, CVE-2026-73626, CVE-2026-67338, CVE-2026-42557, CVE-2026-40171, CVE-2025-59842, CVE-2024-43805, CVE-2024-39700, CVE-2024-22421, CVE-2021-32797 |
| jupyterlab 2.0.0 | CVE-2026-73415, CVE-2026-73626, CVE-2026-67338, CVE-2026-42557, CVE-2026-40171, CVE-2025-59842, CVE-2024-43805, CVE-2024-39700, CVE-2024-22421, CVE-2021-32797 |
Which of your client projects are still on jupyterlab 2.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact jupyterlab version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other jupyterlab versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.