CVE-2026-73416: jupyterlab: PyPI extension blocklist package-name canonicalization bypass

Published Aug 13, 2026
·
Updated

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 blockedextensionsuris 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.

Affected Software

1 affected component
jupyter JupyterLab>=4.5.0<4.5.10, =4.5.10, =4.6.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade jupyterlab to a version that resolves this vulnerability.

    Fixed in 4.5.10
  2. Upgrade

    Upgrade jupyterlab to a version that resolves this vulnerability.

    Fixed in 4.6.2

Event History

Aug 13, 2026
CVE Published
via MITRE·10:04 PM
Data Sourced
via MITRE·10:04 PM
DescriptionWeakness
Data Sourced
via NVD·10:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is CVE-2026-73416?

CVE-2026-73416 is a vulnerability in JupyterLab that allows a bypass of the blocklist for certain PyPI extension package names.

2

What are the versions affected by CVE-2026-73416?

CVE-2026-73416 affects JupyterLab versions 4.5.0 to 4.5.10 and 4.6.2.

3

How do I fix CVE-2026-73416?

To fix CVE-2026-73416, update JupyterLab to a version later than 4.5.10 or 4.6.2.

4

What is the severity level of CVE-2026-73416?

The severity level of CVE-2026-73416 is rated at 37.

5

What are the potential impacts of CVE-2026-73416?

The potential impacts of CVE-2026-73416 include unauthorized installation of blocked PyPI extensions, which can compromise the security of JupyterLab.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203