Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
JupyterLab versions from 4.1.0 up to but not including 4.5.10, and from 4.6.0 up to but not including 4.6.2, let an authenticated user bypass administrator lock rules on the plugin manager. The bypass works by sending direct requests to the plugin API, affecting child plugins of multi-plugin extensions and cases where "lock all" was set, which can allow circumvention of restrictions implemented through locked plugins. Upgrade to JupyterLab 4.5.10 or 4.6.2.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.0 | Medium | 4.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 (VulnCheck) |
- CISA KEV Not listed.
- EPSS 0.0042, the 36th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:09 UTC First seen by agentprime
- 31 Oct 2026, 14:09 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-h5v5-8746-g7mm
- OSV: GHSA-h5v5-8746-g7mm
- github.com/jupyterlab/jupyterlab/security/advisories/GHSA-h5v5-8746-g7mm
- github.com/jupyterlab/jupyterlab/pull/19184
- github.com/jupyterlab/jupyterlab/pull/19185
- github.com/jupyterlab/jupyterlab/pull/19186
- github.com/jupyterlab/jupyterlab/commit/be9303f5bcd5308eaeae953c5a3c903046682c2c
- github.com/jupyterlab/jupyterlab/commit/f1beab4a2027af4719d6edc07d52d6cf5a39a432
- github.com/jupyterlab/jupyterlab
- github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10
- github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2