CVE-2026-102904: JupyterLab: pip option injection enables SSRF/file read

GHSA-3325-v43h-43rvMEDIUM
Published September 29, 2026
CISO Take

JupyterLab's PyPI Extension Manager fails to reject option-like values on uninstall requests, so an authenticated user can inject pip options that make the server read local files or fetch internal URLs, with the content leaking back through error messages. Real-world risk is low: it only applies when the PyPI Extension Manager is enabled and kernels and terminals are disabled or remote, because otherwise the user can already read files and make outbound requests directly. EPSS is 0.00206 (listed as top 90th percentile), the CVE is not in CISA KEV, there is no public exploit or Nuclei template, and SSVC says TRACK. The package has 1,892 dependents and 41 other CVEs, but this issue adds no code execution or availability impact. Upgrade to JupyterLab 4.5.11 or 4.6.4 in hardened multi-user deployments (JupyterHub with locked-down kernels), and disable the PyPI extension manager where it isn't needed.

Sources:NVDGitHub AdvisoryEPSSOpenSSFATLAS

What is the risk?

Medium (CVSS 5.4), and effectively lower in most deployments. It requires an authenticated low-privilege account with extension API access, and it matters only in locked-down setups where kernels and terminals are disabled or remote. Exploitation complexity is low, but the attacker cannot choose arbitrary file content or an arbitrary disclosed line. Confidentiality and integrity impacts are limited: a partial file or URL content leak through parse errors, and creation or corruption of a path via pip log text. There is no public exploit, no KEV listing and a low EPSS value. The main exposure is internal SSRF toward cloud metadata endpoints and internal services from the Jupyter server.

How does the attack unfold?

Initial Access
Attacker authenticates with a low-privilege account that can call the JupyterLab extension API.
AML.T0012
Exploitation
Attacker sends an uninstall request whose name is a pip option such as a requirements or log flag, which passes unvalidated into python -m pip uninstall.
AML.T0049
Collection
The server reads a local file or fetches an internal URL, and pip parse errors reflect the first unparsable line or response content.
AML.T0037
Impact
Partial disclosure of local files or internal service data, plus possible corruption of a chosen path via pip log output.

What systems are affected?

PackageEcosystemVulnerable RangePatched
Jupyterpip—No patch
13.5KOpenSSF 5.71.9K dependentsPushed 7d ago54% patched~27d to patchFull package profile →
Jupyterpip>= 4.6.0, <= 4.6.34.6.4
13.5KOpenSSF 5.71.9K dependentsPushed 7d ago54% patched~27d to patchFull package profile →

How severe is it?

CVSS 3.1
5.4 / 10
EPSS
0.2%
chance of exploitation in 30 days
Higher than 11% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Trivial

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRLow
UINone
SUnchanged
CLow
ILow
ANone

What should I do?

1 step
  1. 1) Upgrade JupyterLab to 4.5.11 or 4.6.4 or later. 2) If patching is delayed, disable the PyPI Extension Manager (set the extension manager to a read-only or disabled mode, or use the --LabApp.extension_manager=readonly style configuration) and restrict access to the extension API at the proxy or hub level. 3) Run the Jupyter server with a least-privilege account, so readable local files do not include secrets. 4) Block egress from the Jupyter host to cloud metadata endpoints (169.254.169.254) and internal admin networks, and enforce IMDSv2. 5) Detection: look in reverse proxy and Jupyter logs for POST requests to the extension API (/lab/api/extensions) whose uninstall name starts with - or -- (for example --requirement, -r, --log), for pip parse errors echoed in responses, and for unexpected pip subprocess executions.

What does CISA's SSVC say?

DecisionTrack
Exploitationnone
AutomatableNo
Technical Impactpartial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Art. 15-Accuracy, robustness and cybersecurity
ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
MANAGE 2.3-Risk treatment and response to unknown risks

Frequently Asked Questions

What is CVE-2026-102904?

JupyterLab's PyPI Extension Manager fails to reject option-like values on uninstall requests, so an authenticated user can inject pip options that make the server read local files or fetch internal URLs, with the content leaking back through error messages. Real-world risk is low: it only applies when the PyPI Extension Manager is enabled and kernels and terminals are disabled or remote, because otherwise the user can already read files and make outbound requests directly. EPSS is 0.00206 (listed as top 90th percentile), the CVE is not in CISA KEV, there is no public exploit or Nuclei template, and SSVC says TRACK. The package has 1,892 dependents and 41 other CVEs, but this issue adds no code execution or availability impact. Upgrade to JupyterLab 4.5.11 or 4.6.4 in hardened multi-user deployments (JupyterHub with locked-down kernels), and disable the PyPI extension manager where it isn't needed.

Is CVE-2026-102904 actively exploited?

No confirmed active exploitation of CVE-2026-102904 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-102904?

1) Upgrade JupyterLab to 4.5.11 or 4.6.4 or later. 2) If patching is delayed, disable the PyPI Extension Manager (set the extension manager to a read-only or disabled mode, or use the `--LabApp.extension_manager=readonly` style configuration) and restrict access to the extension API at the proxy or hub level. 3) Run the Jupyter server with a least-privilege account, so readable local files do not include secrets. 4) Block egress from the Jupyter host to cloud metadata endpoints (169.254.169.254) and internal admin networks, and enforce IMDSv2. 5) Detection: look in reverse proxy and Jupyter logs for POST requests to the extension API (`/lab/api/extensions`) whose uninstall name starts with `-` or `--` (for example `--requirement`, `-r`, `--log`), for pip parse errors echoed in responses, and for unexpected pip subprocess executions.

What systems are affected by CVE-2026-102904?

This vulnerability affects the following AI/ML architecture patterns: Notebook environments, Training pipelines, Multi-tenant JupyterHub deployments, ML development workbenches.

What is the CVSS score for CVE-2026-102904?

CVE-2026-102904 has a CVSS v3.1 base score of 5.4 (MEDIUM). The EPSS exploitation probability is 0.21%.

What is the AI security impact?

Affected AI Architectures

Notebook environmentsTraining pipelinesMulti-tenant JupyterHub deploymentsML development workbenches

MITRE ATLAS Techniques

AML.T0012Valid Accounts
AML.T0037Data from Local System
AML.T0049Exploit Public-Facing Application

Compliance Controls Affected

EU AI Act: Art. 15
ISO 42001: A.6.2.6
NIST AI RMF: MANAGE 2.3

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An attacker with a low-privilege account on a hardened shared JupyterLab service, where terminals and kernels are disabled, sends an uninstall request to the extension API with the name `-r /etc/<file>` or `-r http://169.254.169.254/latest/meta-data/`. The server runs `python -m pip uninstall` with the injected option, tries to parse the target as a requirements file, and returns the first unparsable line or response content in the error message. The attacker repeats this against internal URLs to map the network and collect cloud metadata, then uses a `--log` option to overwrite a chosen path with pip log text to corrupt a configuration file.

Weaknesses (CWE)

CWE-209 — Generation of Error Message Containing Sensitive Information: The product generates an error message that includes sensitive information about its environment, users, or associated data.

  • [Implementation] Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
  • [Implementation] Handle exceptions internally and do not display errors containing potentially sensitive information to a user.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Timeline

Published
September 29, 2026
Last Modified
October 1, 2026
First Seen
September 29, 2026

Related Vulnerabilities