Skip to content
Fencer Vulns
medium 6.0

CVE-2026-73627 json

JupyterLab 4.6.0 Plugin Manager Lock-Rule Enforcement Bypass

published 2026-07-22 3 mo ago modified 2026-10-01 39 d ago also BIT-jupyterlab-2026-73627 , EUVD-2026-57796 , GHSA-h5v5-8746-g7mm

cvss
6.0
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

JupyterLab (pip package 'jupyterlab') versions >=4.1.0,<=4.5.9 and >=4.6.0,<=4.6.1 contain a plugin manager lock-rule enforcement bypass. Two server-side enforcement gaps allow an authenticated user to circumvent administrator lock rules by making direct requests to the /lab/api/plugins endpoint, enabling or disabling plugins that were locked — including child plugins of multi-plugin extensions and plugins locked via the 'lock all' mechanism. This can impact data integrity and bypass hardening or restrictions (e.g., download/upload limits) implemented through locked plugins. Fixed in versions 4.6.2 and 4.5.10.

Patch / fix

  • pypi jupyterlab 4.5.10, 4.6.2
  • bitnami jupyterlab 4.5.10, 4.6.2
  • jupyter jupyterlab 4.5.10, 4.6.2
  • jupyterlab Debian 14 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4

debian advisories DEBIAN-CVE-2026-73627

  • python-jupyterlab openSUSE Tumbleweed 4.5.10-1.1

opensuse advisories openSUSE-SU-2026:11634-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-73627 updated cvss 7.1

jupyterlab: JupyterLab: Plugin manager lock-rule bypass allows unauthorized plugin control

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-th-torch-cpu-py312-rhel9, rhoai/odh-th-torch-cuda-py312-rhel9, rhoai/odh-th-torch-rocm-py312-rhel9, rhoai/odh-th06-cpu-torch291-py312-rhel9
    affected: workaround, no fix available “Lock each plugin individually with jupyter labextension lock <plugin-id> instead of “lock all” or locking only a parent multi-plugin extension. That is the GHSA workaround until you upgrade.”
  • Red Hat OpenShift AI 2.25 rhoai/odh-feature-server-rhel9 1792148523, rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9 1788185839, rhoai/odh-workbench-jupyter-minimal-cuda-py312-rhel9 1788185798, rhoai/odh-workbench-jupyter-minimal-rocm-py312-rhel9 1788185733, rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9 1788185436, rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9 1788185848, +5 more
    fixed: vendor fix “Lock each plugin individually with jupyter labextension lock <plugin-id> instead of “lock all” or locking only a parent multi-plugin extension. That is the GHSA workaround until you upgrade.” RHSA-2026:87410
  • Red Hat OpenShift AI 3.3 rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9 1790260954, rhoai/odh-workbench-jupyter-minimal-cuda-py312-rhel9 1790072130, rhoai/odh-workbench-jupyter-minimal-rocm-py312-rhel9 1790072109, rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9 1789651387, rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9 1789651385, rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9 1790260954, +4 more
    fixed: vendor fix “Lock each plugin individually with jupyter labextension lock <plugin-id> instead of “lock all” or locking only a parent multi-plugin extension. That is the GHSA workaround until you upgrade.” RHSA-2026:73987
  • Red Hat OpenShift AI 3.4 rhoai/odh-feature-server-rhel9 1791863220, rhoai/odh-th06-cpu-torch210-py312-rhel9 1791874335, rhoai/odh-th06-rocm64-torch291-py312-rhel9 1791872119, rhoai/odh-th06-cuda130-torch210-py312-rhel9 1791961113, rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9 1791870673, rhoai/odh-workbench-jupyter-minimal-cuda-py312-rhel9 1791953196, +8 more
    fixed: vendor fix “Lock each plugin individually with jupyter labextension lock <plugin-id> instead of “lock all” or locking only a parent multi-plugin extension. That is the GHSA workaround until you upgrade.” RHSA-2026:84734
  • Red Hat Migration Toolkit for Applications 8 mta/mta-solution-server-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-th06-cuda130-torch291-py312-rhel9, rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9
    not affected: component not present
  • Red Hat OpenShift AI 2.25 rhoai/odh-rhel9-operator 1788331391, rhoai/odh-rhel9-operator 1792570619, rhoai/odh-vllm-cpu-rhel9 1786712073, rhoai/odh-vllm-cpu-rhel9 1792018436, rhoai/odh-dashboard-rhel9 1788312226, rhoai/odh-dashboard-rhel9 1791853525, +132 more Red Hat OpenShift AI 3.3 rhoai/odh-cli-rhel9 1790070206, rhoai/rhai-cli-rhel9 1790070206, rhoai/odh-mlflow-rhel9 1789653606, rhoai/odh-trainer-rhel9 1790136369, rhoai/odh-maas-api-rhel9 1790131842, rhoai/odh-mlserver-rhel9 1789121365, +67 more Red Hat OpenShift AI 3.4 rhoai/odh-cli-rhel9 1791509689, rhoai/rhai-cli-rhel9 1791509689, rhoai/odh-automl-rhel9 1791535789, rhoai/odh-mlflow-rhel9 1791865967, rhoai/odh-autorag-rhel9 1791557539, rhoai/odh-trainer-rhel9 1791869783, +86 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 6.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
CNA 4.0 6.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
pypi jupyterlab
>=4.6.0, <4.6.2
>=4.1.0, <4.5.10
4.6.2
4.5.10
bitnami jupyterlab
>=4.1.0, <4.5.10
>=4.6.0, <4.6.2
4.5.10
4.6.2

Affected products

  • jupyterlab jupyterlab

Classification

Weakness
  • CWE-602 Client-Side Enforcement of Server-Side Security
  • CWE-863 Incorrect Authorization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.