Vulnerability in jupyterlab (DEBIAN-CVE-2026-73626)

Summary

Vulnerability in jupyterlab (DEBIAN-CVE-2026-73626). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4 or later.

Original description

The description as published by the source.

JupyterLab versions >=4.6.0,<=4.6.1 and <=4.5.9 contain an allowlist/blocklist enforcement gap in PyPIExtensionManager.install(). A missing 'await' caused the is_install_allowed coroutine to never execute, so the extension allowlist/blocklist check was not enforced for direct callers of install(). The stock JupyterLab HTTP API and Extension Manager UI are not affected, as they perform a separate, correctly awaited check. The issue affects only deployments where a custom extension or downstream integration imports PyPIExtensionManager and calls install() directly with a package name influenced by untrusted input, an allowlist/blocklist is configured, the PyPI Extension Manager is enabled, and kernels and terminals are disabled or delegated to remote hosts. Fixed in JupyterLab 4.6.2 and 4.5.10.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2026-73626 has been found in jupyterlab.
Successful exploitation can lead to full system takeover.
What to do: upgrade jupyterlab to 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4 or later.
If unsure, ask your IT team or search "jupyterlab DEBIAN-CVE-2026-73626" on the vendor's site.

DEBIAN-CVE-2026-73626 (jupyterlab)
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4 — 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 (unclassified) exists in jupyterlab.

📍 Affected scope

Check the vendor advisory for the affected versions of jupyterlab.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4.

🛡️ 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
Identify exposure identify
```
grep -r 'jupyterlab' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で jupyterlab を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade jupyterlab to 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4
```
ステージング環境で 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:13 jupyterlab

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:14 jupyterlab

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4"}]}]

References

advisory security-tracker.debian.org