Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 6, published 22 July 2026.
- Which products and versions are affected?
- Project Jupyter JupyterLab >= 4.1.0, <= 4.5.9; >= 4.6.0, <= 4.6.1.
- Is there a fix for This vulnerability?
- A patch was published on 2026-07-22. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run Project Jupyter JupyterLab at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
JupyterLab contains an incorrect authorization vulnerability (CWE-863) and client-side enforcement of server-side security (CWE-602) in its PluginManager. Authenticated users can bypass administrative 'lock' rules by making direct requests to the `/lab/api/plugins` endpoint. This bypass is possible for child plugins of extensions covering multiple plugins or when a 'lock all' rule is active. Attackers can use this to re-enable plugins that were disabled for security hardening, such as those enforcing resource limits. The issue is patched in versions 4.6.2 and 4.5.10.
Affected products
- Jupyter jupyterlab >= 4.1.0, <= 4.5.9; >= 4.6.0, <= 4.6.1
Timeline
- 2026-07-21: disclosed
- 2026-07-22: advisory: GitHub Advisory GHSA-h5v5-8746-g7mm published
- 2026-07-22: patched