Client-Side Enforcement of Server-Side Security Affecting jupyterlab package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN13-JUPYTERLAB-18767478
- published14 Aug 2026
- disclosed13 Aug 2026
Introduced: 13 Aug 2026
CVE-2026-73627 (opens in a new tab)How to fix?
There is no fixed version for Debian:13 jupyterlab.
NVD Description
Note: Versions mentioned in the description apply only to the upstream jupyterlab package and not the jupyterlab package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
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.