UTC
Medium

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
What it is

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.

What to do

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.

If you cannot upgrade yet

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.

Affected
PackageRegistryAffectedFixed in
jupyterlabPyPI>= 4.0.0, <= 4.5.104.5.11
jupyterlabPyPI>= 4.6.0, <= 4.6.34.6.4

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].