JupyterLab up to 4.5.9/4.6.1 PyPI Extension Manager manager.py privileges management

Summaryinfo

A vulnerability was found in JupyterLab up to 4.5.9/4.6.1. It has been classified as problematic. Impacted is an unknown function of the file jupyterlab/extensions/manager.py of the component PyPI Extension Manager. The manipulation leads to privileges management. This vulnerability is listed as CVE-2026-73416. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in JupyterLab up to 4.5.9/4.6.1. It has been rated as problematic. This issue affects an unknown code block of the file jupyterlab/extensions/manager.py of the component PyPI Extension Manager. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is integrity, and availability. The summary by CVE is:

jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 4.5.0 until 4.5.10 and 4.6.2, in jupyterlab/extensions/manager.py and jupyterlab/extensions/pypi.py, JupyterLab's PyPI extension manager enforces blocked_extensions_uris by comparing requested install names to blocklist entries with custom normalization that is weaker than PyPI package-name canonicalization. An authenticated user can request a PyPI-equivalent spelling such as JupyterLab.Git for a blocklisted package such as jupyterlab-git, and JupyterLab accepts the install request even though pip resolves the variant to the same package. Security impact requires an allowlist or blocklist intended to restrict package installation, the PyPI Extension Manager, and kernels and terminals that are disabled or delegated to remote hosts. The bypass lets an authenticated user install a prohibited extension, defeat integrity restrictions, and affect availability without gaining new read access. This issue is fixed in versions 4.5.10 and 4.6.2.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-73416 since 08/12/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 4.5.10 or 4.6.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• JupyterLab

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 4.5.7
• 4.5.8
• 4.5.9
• 4.6.0
• 4.6.1

Website

• Product: https://github.com/jupyterlab/jupyterlab/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion