Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73416

Vulnerability in jupyterlab (CVE-2026-73416)

Summary

Vulnerability in jupyterlab (CVE-2026-73416). Risk of unauthorized operations or information disclosure. Exploitable via blocked_extensions_uris. Mitigation: upgrade to 4.5.10 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73416 has been found in jupyterlab.
Attackers can target a specific entry point like blocked_extensions_uris over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade jupyterlab to 4.5.10 or later.
If unsure, ask your IT team or search "jupyterlab CVE-2026-73416" on the vendor's site.

CVE-2026-73416 (jupyterlab) — CWE-178
Attack surface: blocked_extensions_uris / JupyterLab.Git / jupyterlab
Patched: 4.5.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-178) exists in jupyterlab. Attackers reach the vulnerable code path via blocked_extensions_uris.

📍 Affected scope

Check the vendor advisory for the affected versions of jupyterlab. Attack surface: blocked_extensions_uris / JupyterLab.Git / jupyterlab.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.5.10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jupyterlab' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'jupyterlab' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で jupyterlab を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade jupyterlab to 4.5.10

    ステージング環境で 4.5.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip jupyterlab
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.10"}]}]
Bitnami jupyterlab
[{"type":"SEMVER","events":[{"introduced":"4.5.0"},{"fixed":"4.5.10"},{"introduced":"4.6.0"},{"fixed":"4.6.2"}]}]
PyPI jupyterlab
[{"type":"ECOSYSTEM","events":[{"introduced":"4.5.0"},{"fixed":"4.5.10"},{"introduced":"4.6.0"},{"fixed":"4.6.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details