CVE-2026-102904

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 30, 2026

Advisory Details (5)

Auto-updated Sep 29, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v4.6.4

Patch available: jupyterlab/jupyterlab v4.6.4

https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4
github_release Patch Available

v4.5.11

Patch available: jupyterlab/jupyterlab v4.5.11

https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11
github_commit

commit e277bc958e73 (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit e277bc958e73 — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/e277bc958e737130ac47b6c5078d08b29298828f
github_commit

commit a274a8276b91 (jupyterlab/jupyterlab)

Fix landed in jupyterlab/jupyterlab commit a274a8276b91 — awaiting tagged release

https://github.com/jupyterlab/jupyterlab/commit/a274a8276b9185d03efd4c3c20713d3137ac49e6
github Patch Available

Argument injection in JupyterLab extension uninstall exposes server-readable files and internal URLs · Advisory · jupyterlab/jupyterlab · GitHub

Affected: 4.5.7

https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-3325-v43h-43rv

Vendor Advisories for CVE-2026-102904(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
jupyterlab4.6.0, 4.6.1, 4.6.2, 4.6.34.6.4—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 03:46 UTCEG score recompute
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-03 01:54 UTCEG score recompute
  4. 2026-10-02 00:01 UTCEG score recompute
  5. 2026-10-01 19:49 UTCEPSS rescore
  6. 2026-09-30 21:29 UTCEG score recompute
  7. 2026-09-30 20:27 UTCEG score recompute
  8. 2026-09-30 15:02 UTCEPSS rescore
  9. 2026-09-29 21:21 UTCEG score recompute
  10. 2026-09-29 20:59 UTCEG score recompute
  11. 2026-09-29 20:58 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-102904?
CVE-2026-102904 is a medium vulnerability published on September 29, 2026. 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…
When was CVE-2026-102904 disclosed?
CVE-2026-102904 was first published on September 29, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102904 actively exploited?
CVE-2026-102904 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102904?
CVE-2026-102904 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102904?
A fix for CVE-2026-102904 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102904 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102904

Explore →

Is Your Infrastructure Affected by CVE-2026-102904?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs