High [CVE-2026-73627] Plugin manager lock-rule bypass allows unauthorized plugin control
This high-severity Red Hat Linux advisory covers CVE-2026-73627 affecting Red Hat OpenShift AI 2.25, Migration Toolkit for Applications 8, Red Hat OpenShift AI (RHOAI).
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
JupyterLab (pip package 'jupyterlab') versions >=4.1.0, =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.
A flaw was found in JupyterLab. Direct API requests can enable or disable plugins intended to be locked, impacting data integrity and bypassing security restrictions in Red Hat OpenShift AI and Migration Toolkit for Applications deployments.
Red Hat severity: Moderate — CVSS 7.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N). Weakness: CWE-414.
Affected Red Hat products: Red Hat OpenShift AI 2.25; Migration Toolkit for Applications 8; Red Hat OpenShift AI (RHOAI). Red Hat fixing advisory: RHSA-2026:65126.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 27 days ago·verify at source
- 4.6.2
- 4.5.10
- rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9:1788315638
- 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-llmcompressor-cuda-py312-rhel9:1788185842
- rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9:1788185848
- rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9:1788186007
- rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9:1788185846
- rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:1788185899
- RHSA-2026:65126
Official advisory · high-confidence parse· fetched 27 days ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 27 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.