jupyterlab vulnerabilities
JupyterLab computational environment
- Registry
- PyPI
- Latest
- 4.6.6
- License
- BSD License
19 known advisories
The latest version, 4.6.6, is not affected by any of them. Projects on older versions may be.
pip install 'jupyterlab>=4.6.6'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
Security advisories for jupyterlab
JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked
- Affected
- >=4.6.0 <4.6.4 · >=4.5.7 <4.5.11
- Fixed in
- 4.5.11, 4.6.4
JupyterLab: Cross-site scripting (XSS) in JupyterLab via crafted language package (jupyterlab.json)
- Affected
- >=4.6.0 <4.6.4 · >=3.0.0 <4.5.11
- Fixed in
- 4.5.11, 4.6.4
JupyterLab: Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs
- Affected
- >=4.6.0 <4.6.4 · >=4.0.0 <4.5.11
- Fixed in
- 4.5.11, 4.6.4
JupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboard
- Affected
- >=4.6.0 <4.6.4 · >=4.5.0 <4.5.11
- Fixed in
- 4.5.11, 4.6.4
JupyterLab: Cross-site scripting (XSS) via crafted settings file (`overrides.json`)
- Affected
- >=4.6.0 <4.6.2 · >=3.3.0 <4.5.10
- Fixed in
- 4.5.10, 4.6.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: PyPI extension blocklist package-name canonicalization bypass
- Affected
- >=4.6.0 <4.6.2 · >=4.5.0 <4.5.10
- Fixed in
- 4.5.10, 4.6.2
JupyterLab PluginManager lock-rule enforcement bypass
- Affected
- >=4.6.0 <4.6.2 · >=4.1.0 <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
JupyterLab has an Extension Manager API/GUI Policy Discrepancy, allowing 3rd party (malicious) extensions install via POST request
- Affected
- >=4.0.0 <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 vulnerable to SXSS in Markdown Preview
- Affected
- >=4.0.0 <4.0.11
- Fixed in
- 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
Is your jupyterlab version vulnerable?
- jupyterlab 4.6No known advisories in 4.6.6
- jupyterlab 4.5No known advisories in 4.5.11
- jupyterlab 4.410 advisories in 4.4.10
- jupyterlab 4.311 advisories in 4.3.8
- jupyterlab 4.212 advisories in 4.2.7
- jupyterlab 4.113 advisories in 4.1.8
- jupyterlab 3.69 advisories in 3.6.8
- jupyterlab 3.511 advisories in 3.5.3
- jupyterlab 3.411 advisories in 3.4.8
- jupyterlab 3.311 advisories in 3.3.4
- jupyterlab 3.210 advisories in 3.2.9
- jupyterlab 3.110 advisories in 3.1.19
- jupyterlab 2.39 advisories in 2.3.2
- jupyterlab 2.29 advisories in 2.2.10
- jupyterlab 2.110 advisories in 2.1.5
- jupyterlab 2.010 advisories in 2.0.2
Which of your client projects still run an old jupyterlab?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.