Skip to content
Threat Brief

← All advisories

CVE-2026-73627

Medium 6.0No known exploitationFix available

JupyterLab 4.1.0 before 4.5.10 and 4.6.0 before 4.6.2 Plugin Manager Lock-Rule Enforcement Bypass

Record last updated

CVSS score

6.0

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 37% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-602

Patching and mitigation

Patch status
Fix available (source: CVE record (VulnCheck))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
jupyterlabjupyterlabfrom 4.1.0 before 4.5.104.5.10CVE Program
jupyterlabjupyterlabfrom 4.6.0 before 4.6.24.6.2CVE Program

Timeline

  1. Disclosure

    CVE record published by VulnCheck

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (VulnCheck)

    Source: CVE record (VulnCheck) (opens in a new tab)

Vendor guidance and references

CVE-2026-73627: JupyterLab 4.1.0 before 4.5.10 and 4.6.0 before 4.6.2 Plugin Manager Lock-Rule Enforcement Bypass · Threat Brief