An authenticated user can make direct requests to the /lab/api/plugins endpoint and alter the enabled status of plugins that are locked by administrator rules. The vulnerability stems from gaps in server‑side lock‑rule enforcement, allowing the bypass of both individual plugin locks and the ‘lock all’ mechanism. This leads to unauthorized modification of plugin state, which can compromise data integrity and allow an attacker to override hardening restrictions such as download or upload limits. The weakness is cataloged as CWE‑602 and CWE‑414.

The issue affects the JupyterLab pip package named jupyterlab, for all releases from version 4.1.0 through 4.5.9 inclusive and from 4.6.0 through 4.6.1 inclusive. The vulnerability is fixed in version 4.5.10 and 4.6.2. The affected vendor is Jupyter, and the impacted product is the JupyterLab desktop and web application.

The CVSS base score of 6 indicates a medium severity with the potential for moderate impact on confidentiality, integrity, and availability. Because the vulnerability requires authentication to the JupyterLab instance, the attack vector is server‑side; a malicious user with user privileges can target the API endpoint directly. The EPSS score is 0.00249, indicating a low likelihood of exploitation, and the vulnerability is not listed in CISA’s KEV catalog, suggesting that prior exploitation is not widely observed. Nonetheless, the ability to lift administrative locks poses a tangible risk for environments where strict plugin policy enforcement is critical.