Skip to content
Heist/ feed
Back to feed
MediumFix available

JupyterLab: Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs

Type: advisorySources: OSV

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.

Products
jupyterlab
Affected versions
Not specified
Fixed versions
4.5.11, 4.6.4
CVEs
CVE-2026-102904
Confirmed fixed CVEs
Not specified
Updated in this feed
27 Oct 2026, 11:22 UTC · Revision 1

Source evidence

JupyterLab: Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs

core-osv · Original source

Published 6 Oct 2026, 11:44 UTC

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.

osv:BIT-jupyterlab-2026-102904

jupyterlab

Fixed versions: 4.5.11, 4.6.4

Complete source record
{
  "id": "4e41016c7a2e34bc091cfa045d7b4a1cb54736c9aa4e714336c35eed0dba6d9c",
  "url": "https://osv.dev/vulnerability/BIT-jupyterlab-2026-102904",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "JupyterLab: Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs",
    "summary": "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.",
    "evidence": "osv:BIT-jupyterlab-2026-102904",
    "products": [
      {
        "name": {
          "value": "jupyterlab",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "4.5.11",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "4.6.4",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "BIT-jupyterlab-2026-102904",
      "aliases": [
        "BIT-jupyterlab-2026-102904",
        "CVE-2026-102904",
        "GHSA-3325-v43h-43rv",
        "PYSEC-2026-4055"
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "4.0.0"
                },
                {
                  "fixed": "4.5.11"
                },
                {
                  "introduced": "4.6.0"
                },
                {
                  "fixed": "4.6.4"
                }
              ]
            }
          ],
          "package": {
            "name": "jupyterlab",
            "purl": "pkg:bitnami/jupyterlab",
            "ecosystem": "Bitnami"
          },
          "severity": [
            {
              "type": "CVSS_V3",
              "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N"
            }
          ],
          "database_specific": {
            "source": "https://github.com/bitnami/vulndb/tree/main/data/jupyterlab/BIT-jupyterlab-2026-102904.json"
          }
        }
      ],
      "modified": "2026-10-06T15:25:39.595262795Z",
      "provider": "osv",
      "references": [
        "https://github.com/jupyterlab/jupyterlab/commit/a274a8276b9185d03efd4c3c20713d3137ac49e6",
        "https://github.com/jupyterlab/jupyterlab/commit/e277bc958e737130ac47b6c5078d08b29298828f",
        "https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11",
        "https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4",
        "https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-3325-v43h-43rv",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-102904"
      ],
      "provider_metadata": {
        "cpes": [
          "cpe:2.3:a:jupyter:jupyterlab:*:*:*:*:*:python:*:*"
        ],
        "severity": "Medium"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-102904",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/database_specific/severity"
  },
  "source_id": "core-osv",
  "document_id": 89143,
  "published_at": "2026-10-06T11:44:18.332+00:00"
}