CVE-2026-102904 JupyterLab: Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs
Authenticated users can inject pip options to read local files or access internal URLs via the extension uninstall API.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-102904?
CVE-2026-102904 is a medium-severity server-side request forgery vulnerability in jupyterlab, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From JupyterLab 4.0.0 until 4.5.11 and 4.6.4, the PyPI Extension Manager uninstall request reaches ExtensionHandler.post, which validates extension names for installation but passes uninstall names to PyPIExtensionManager.uninstall and python -m pip uninstall without rejecting option-like values. The security impact requires that the PyPI Extension Manager is enabled, the account can call the extension API, and kernels and terminals are disabled or delegated to remote hosts; otherwise the user can already read files and make outbound requests directly. An authenticated user with extension API access can supply a pip requirements option to make the server read a local file or fetch an internal URL, and reflected parse errors can return the first unparsable line or response content. A pip log option can also create or corrupt a chosen path with pip-generated log text, but the requester cannot select an arbitrary disclosed line or arbitrary file content, and the injection does not add code execution or availability impact beyond ordinary package removal. This issue is fixed in JupyterLab 4.5.11 and 4.6.4.
Which versions are affected by CVE-2026-102904?
6 open source packages ship an affected version, including jupyterlab.
| Package | Affected | Fixed in |
|---|---|---|
jupyterlab Bitnami | From 4.0.0 | 4.5.11, 4.6.4 |
jupyterlab PyPI | From 4.0.0 | 4.5.11, 4.6.4 |
jupyterlab PyPI | From 4.0.0 | 4.5.11 |
jupyterlab PyPI | From 4.0.0 | 4.5.11 |
jupyterlab PyPI | From 4.6.0 | 4.6.4 |
jupyterlab PyPI | From 4.6.0 | 4.6.4 |
How do I fix CVE-2026-102904?
Upgrade jupyterlab to a fixed version for your release line: 4.5.11 or 4.6.4.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-102904 being exploited?
There is no known exploitation of CVE-2026-102904 in the wild and no public exploit code.
Sources
Also known as BIT-jupyterlab-2026-102904, DEBIAN-CVE-2026-102904, GHSA-3325-v43h-43rv, MINI-69fp-9cvp-r6jx, MINI-p3g5-632r-3g6p, PYSEC-2026-4055 and 1 more.