CVSS 3.1
5.4 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NMedium (5.4) in jupyterlab jupyterlab. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in jupyterlab 4.5.11, 4.6.4.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:Njupyterlab (PyPI): fixed in 4.6.4, 4.5.11Explain CVE-2026-102904 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102904?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102904?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102904 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| jupyterlab | >= 4.0.0, < 4.5.11 |
| jupyterlab | >= 4.6.0, < 4.6.4 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-3325-v43h-43rv | PyPI | jupyterlab | >=4.6.0 <4.6.4 | 4.6.4 |
| GHSA-3325-v43h-43rv | PyPI | jupyterlab | >=4.0.0 <4.5.11 | 4.5.11 |
| PYSEC-2026-4055 | PyPI | jupyterlab | >=4.0.0 <4.5.11 >=4.6.0 <4.6.4 | 4.5.11, 4.6.4 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13, 14 | jupyterlab | no fix listed | DEBIAN-CVE-2026-102904 |
| Ubuntu | 26.04:LTS, 26.10 | jupyterlab | no fix listed | UBUNTU-CVE-2026-102904 |
| openSUSE | Tumbleweed | python-jupyterlab | 4.5.11-1.1 | openSUSE-SU-2026:11945-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Moderate.
A moderate-impact argument injection flaw in JupyterLab affects Red Hat OpenShift AI, which ships the vulnerable JupyterLab releases in its workbench and distributed-workload notebook images, and the Migration Toolkit for Applications 8.1 solution server image, which also ships JupyterLab. When JupyterLab processes an extension uninstallation request through the PyPI Extension Manager, the user-supplied extension name is passed to `python -m pip uninstall` without rejecting option-like values. An authenticated user permitted to call the extension API can exploit this to inject pip command-line options: a requirements option such as `-r` makes the server read a local file or fetch an internal URL, with pip's reflected parse error returning the first unparsable line and the path to the requester, and a log option such as `--log` can create or corrupt a chosen path with pip-generated log text. The requester cannot choose which line of a file is disclosed and cannot write content of their choosing, and the injection adds no code execution or availability impact beyond what the extension manager already permits. The issue has security implications only where 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 such users can already read the same files and make the same outbound requests directly. Red Hat rates this flaw Moderate with a CVSS 3.1 score of 5.4, matching the upstream severity. Because the impact is Moderate with a CVSS score below 7.0, fixes for the affected Red Hat OpenShift AI components are deferred, leaving a residual risk of local file disclosure, internal network probing, and pip log file corruption by authenticated users with extension API access. The affected Migration Toolkit for Applications 8.1 stream is out of support scope.
Upstream provides a workaround: deployments can disable programmatic extension installation and removal entirely by switching JupyterLab to the read-only extension manager, either by starting the server with the `--LabApp.extension_manager=readonly` command-line option or by setting the traitlet `c.LabApp.extension_manager = 'readonly'` in the JupyterLab configuration file. Because exploitation requires an authenticated account able to call the extension API, restricting extension API access to trusted accounts also reduces exposure. This issue is fixed upstream in JupyterLab 4.5.11 and 4.6.4; the fix for the affected Red Hat OpenShift AI components is deferred, so the read-only extension manager remains the available mitigation in the interim.
| Product | Package | State | Advisory |
|---|---|---|---|
| Migration Toolkit for Applications 8 | mta/mta-solution-server-rhel9 | Out of support scope | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-feature-server-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cpu-torch210-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cpu-torch291-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cuda130-torch210-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cuda130-torch291-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-rocm64-torch291-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-cpu-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-cuda-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-rocm-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-minimal-cuda-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-minimal-rocm-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9 | Fix deferred | |
| 1 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102904.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.