JupyterLab: Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs
CVE-2026-102904 · GHSA-3325-v43h-43rv · published 2026-10-01
- Severity
- Medium
- CVSS score
- 5.4
- Chance of exploitation (EPSS)
- 0.21%
- Fixed in
- 4.6.4
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
An authenticated user gains a read of server-side files and an outbound request from the server, both outside the confinement that the contents root and the disabled kernels were meant to provide. The user cannot choose which line of a file is returned, and cannot write content of their choosing.
Upgrade jupyterlab to 4.6.4 or later.
JupyterLab v4.6.4 and v4.5.11 contain the patch. The uninstall name is now validated as a PyPI package name in both the HTTP handler and PyPIExtensionManager.uninstall, and the pip command line carries an explicit -- before the package operand. Users of applications that depend on JupyterLab, such as Notebook v7+, should update jupyterlab package too.
Deployments wanting to disable programmatic extension installation and removal entirely can switch to the read-only extension manager: --LabApp.extension_manager=readonly or the following traitlet: c.LabApp.extension_manager = 'readonly' You can confirm that the read-only manager is in use from GUI: Users lose the ability to install and remove extensions from the Extension Manager; extensions must then be installed by an administrator in the environment. Note: an egress policy that blocks outbound requests from the single-user server limits the reach of the URL variant, but does not address the file read or the file write.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| jupyterlab | PyPI | >= 4.0.0, <= 4.5.10 | 4.5.11 |
| jupyterlab | PyPI | >= 4.6.0, <= 4.6.3 | 4.6.4 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- HighJupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboardjupyterlab, jupyterlab, notebook
- HighJupyterLab: Image viewer allows XSS when opening malicious image in new browser tabjupyterlab, jupyterlab
- HighJupyterLab: Cross-site scripting (XSS) via crafted settings file (`overrides.json`)jupyterlab, jupyterlab
- HighJupyterLab's command linker attributes in HTML enable one-click command execution from untrusted contentjupyterlab, notebook
- HighJupyterLab has an Extension Manager API/GUI Policy Discrepancy, allowing 3rd party (malicious) extensions install via POST requestjupyterlab
- HighJupyter Notebook Vulnerable to Authentication Token Theft via CommandLinker XSSjupyterlab, notebook
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.