Is jupyterlab 4.6 vulnerable?
PyPI · 7 releases from 4.6.0 to 4.6.6 · latest jupyterlab is 4.6.6 · checked 18 Nov 2026
No known advisories in the last release
jupyterlab 4.6.6, the last 4.6 release, has no known advisories. 9 advisories affect earlier 4.6.x releases, so update to 4.6.6.
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
Fixed within 4.6.x, affecting earlier releases
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
Every jupyterlab 4.6.x release
Affected: 4.6.0 to 4.6.3. 4.6.4 and later are not affected.
| Version | Known advisories |
|---|---|
| jupyterlab 4.6.6 | None |
| jupyterlab 4.6.5 | None |
| jupyterlab 4.6.4 | None |
| jupyterlab 4.6.3 | CVE-2026-102832, CVE-2026-102830, CVE-2026-102904, CVE-2026-102831 |
| jupyterlab 4.6.2 | CVE-2026-102832, CVE-2026-102830, CVE-2026-102904, CVE-2026-102831 |
| jupyterlab 4.6.1 | CVE-2026-102832, CVE-2026-102830, CVE-2026-102904, CVE-2026-102831, CVE-2026-73417, CVE-2026-73415, CVE-2026-73416, CVE-2026-73627, CVE-2026-73626 |
| jupyterlab 4.6.0 | CVE-2026-102832, CVE-2026-102830, CVE-2026-102904, CVE-2026-102831, CVE-2026-73417, CVE-2026-73415, CVE-2026-73416, CVE-2026-73627, CVE-2026-73626 |
Which of your client projects are still on jupyterlab 4.6?
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.